Topic: Database problem with Recorder 2002

We've just had a severe problem with Recorder 2002.  I was using the taxon dictionary to look up species names when it crashed.  Unhandled error - nothing unusual there, it happens all the time.  Everything stopped working, so I closed Recorder & tried to re-open it.  It complained that Recorder was still running on my machine, so it couldn't open it.  I restarted the computer & tried again - and got the following error message:

An error occured when starting the application.
ETDBEngineError: Access status 3343 - unregonised database format. 
'N:\Rec2002\Database\nbndict.mdb'.
DBI Error Code = Titan (BDE) Error 3343

Recorder now won't open on any of our computers.  Our IT manager is off sick (why do computers always stop working when the IT staff are away?)

We have recently moved office, and have got a new server.  Our system has been rather unstable, and we have had endless problems with the e-mail and things running very slow.

The new server has meant that we had to spend a lot of time correcting file paths in the registry before we could get Recorder working - but it seemed to be working OK.  The file path that it has given in the error message looks like the old file path - when we were updating the file paths in the registry we were using G:\NDrive\Rec 2002.  I have had a look in the registry and the 'database path', 'CD database path' and 'Dict images path' are all using the N:\Rec2002\Database filepath.  I was wondering if this was the problem, but don't want to fiddle around with anything and cause more problems!

Does any of this mean anything to anyone - and do you have any suggestions?  I have a member of staff going quietly mad because she cannot input any data and her e-mail has also gone down, so she can't do most of her work!

Ellie
Eleanor Knott
Senior Records Centre Officer
Devon Biodiversity Records Centre

Eleanor Knott
Specialist Officer
Devon Biodiversity Records Centre
01392 274128

Re: Database problem with Recorder 2002

Ellie,

Manually correcting the paths in the registry should be safe to do - I've recently done some myself after a server transfer. Just make sure you back up the registry first! I'm afraid I don't know what has caused this problem though.

Regards,
Dave

Dave Slade
Senior IT & Records Officer,  SEWBReC
13 St Andrews Crescent, Cardiff, CF10 3DB

Re: Database problem with Recorder 2002

Sounds like the database may have been corrupted. That error message also reminds me of the one you get if you open NBNData.mdb in a version of Access greater than Access 97 and do a "convert database". Are you able to open the database in Access?

Failing that, try restoring from backup and swapping the failing database with your backed up one.

Charles

Re: Database problem with Recorder 2002

Thanks for the replies - it turned out that the species dictionary had corrupted, so we replaced it with one from the backup tape.  It's all working now, thank heavens (& IT managers!)

Ellie

Eleanor Knott
Specialist Officer
Devon Biodiversity Records Centre
01392 274128

5

Re: Database problem with Recorder 2002

Hi,

I recently faced similar problem, but unfortunately, I don't have a backup. I then tried a utility called Advanced Access Repair. It works rather well for my corrupt MDB file. Its web address is http://www.datanumen.com/aar/ So I think this might be useful for other people like me. Good luck!

Alan