John Colby
jcolby at colbyconsulting.com
Thu Oct 23 15:46:44 CDT 2003
Charlotte, I guess I should have been more clear, it isn't everywhere. This is a large database with many tables. All but one form function fine. In a very brief google of the symptoms I came up with "corrupted memo field" as the most probable cause with the jetcomp program fixing it. Unfortunately jetcomp wouldn't run so it didn't fix it. Unfortunately if you have this problem somewhere in your db, it causes nasty symptoms. The fields one by one go to #error with a jet error reported each time. No way out but click the OK button each time. Even when all done, if you hang around in the form, the error will pop up again and again, every 10-15 seconds. I have no doubt that the problem behind the problem is a corrupt memo field, but the fact is that 3 of 5 computers don't display the problem, in fact 4 of 6. I just checked my server here at my office and it has sp1 as well, the db runs fine here. Those that do display the problem have SP2, the rest SP1. John W. Colby www.colbyconsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte Foust Sent: Thursday, October 23, 2003 4:03 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Win2K, Access 2002 SP2 I have SP2 installed and don't get that message on either Win2k or WinXP. What Jet service pack is applied? Charlotte Foust -----Original Message----- From: John Colby [mailto:jcolby at colbyconsulting.com] Sent: Thursday, October 23, 2003 9:36 AM To: AccessD Subject: [AccessD] Win2K, Access 2002 SP2 I just wanted to give a heads up - I have a client that is using Office 2002. He is getting the JET error "the operation was halted because you and another user...". This error only occurs on machines that have SP2 applied (2 out of 5) whereas those with SP1 (3 of 5) don't get the error. The error occurs as the data is being saved into the table, after AfterUpdate. Oddly enough the data did go in to the table. Nothing obvious, compacted / repaired the BE and FE using the built-in compact etc. The standalone compact/repair program failed early on (immediately). I do not know for sure that it is a SP issue, however those that had SP1 worked, those with SP2 failed. Since I only have 5 machines it isn't a done deal that this is the issue. On the other hand I was loath to break a functioning machine by applying the SP2 to one of those that worked to see if it broke. I did try uninstalling, then reinstalling and applying only SP1. The machine still failed. Likewise not conclusive evidence since uninstall leaves trash behind. John W. Colby www.colbyconsulting.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com