Panic! Today this error 3343 appeared and we are trying to rescue the database with the JetCompUtility.
(Multiuser-Environment Frontend MDE, Backend MDB, all Machines run NT4 and Access 2000.)
Does anybody have clue (experience) how was this Corruption was created? I read some Threads and a Microsoft Article about DAO/ADO References in the VBA Code to check.
Well the Application/MDE uses Microsoft DAO 3.6 Object Library and no ADO or other database libraries...
Some Clients are still using Office97 but they don't have any database access...
Most in-code database activity is done via DAO Recordsets with dbOpenDynaset. Can this maybe cause synchronisation problems when more user try to access the database?...
(Multiuser-Environment Frontend MDE, Backend MDB, all Machines run NT4 and Access 2000.)
Does anybody have clue (experience) how was this Corruption was created? I read some Threads and a Microsoft Article about DAO/ADO References in the VBA Code to check.
Well the Application/MDE uses Microsoft DAO 3.6 Object Library and no ADO or other database libraries...
Some Clients are still using Office97 but they don't have any database access...
Most in-code database activity is done via DAO Recordsets with dbOpenDynaset. Can this maybe cause synchronisation problems when more user try to access the database?...