ESdat Forums
»
Forums
»
ESdat
»
23280 unrecognised database format
 Rank: Newbie
Groups: Registered
Posts: 3
Location: Perth, WA, Australia
|
Good morning, We've received an unexpected error: 23280 Unrecognised Database Format 'file path'. We didn't experience any issues when previously working in the database, and it all appeared to close down as normal last night. When browsing to the file in Explorer, there is an access locking file ".ldb", but no one else is using or attempting to use the database. Has anyone come across this before? Regards, Paul
|
|
|
|
|
|
Rank: Administration
Groups: Registered, Administrators
Posts: 259
Location: Ballina
Was thanked: 8 time(s) in 8 post(s)
|
Hello Paul, Occasionally an Access database may exhibit unexpected bahaviour (usually due to some network issue while saving data). Please have a look at the following for recovery options. http://www.ESdat.net/ESdathelp/index.html?resolving_problems.htm In particular the link to: JETCOMP.exe utility available from Microsoft (at http://support.microsoft.com/kb/295334/en-us If that tool isn't able to recover the database it is likely that you will have to recover it from backup. You can open the .ldb file in MS Word to see information when it was last used. Sincerely, Alex Edited by user Wednesday, July 11, 2012 11:44:14 PM(UTC)
| Reason: Not specified
|
|
|
|
|
|
Rank: Newbie
Groups: Registered
Posts: 3
Location: Perth, WA, Australia
|
Hi Alex, I installed JetCOMP and attempted to compact the database file, but it was unsuccessful. When opening the .ldb file in word, i'm only given one line of text with what i'm assuming is the computer name and user name. not looking good so far! Any other ideas?
|
|
|
|
|
|
Rank: Administration
Groups: Registered, Administrators
Posts: 259
Location: Ballina
Was thanked: 8 time(s) in 8 post(s)
|
Hello Paul, Unfortunately if JetCOMP cant recover it the only resolution is to restore the database from backup. Once you have restored it, open it in ESdat and do a Compact and Repair on it (File menu). Create your own backups of this one for a while, especially after doing data imports, (just in case the issue was something other than a network glitch while writing data). The easiest way to do this is in ESdat: File - Export - Zip. If it still shows any signs of anything strange it might be necessary to migrate the data into a fresh database using a Data Interchange File. Sincerely, Alex
|
|
|
|
|
|
Rank: Newbie
Groups: Registered
Posts: 3
Location: Perth, WA, Australia
|
Hi Alex, We ended up recovering the file from backup, but only lost about 4 hours worth of work. Thanks for your help, Paul
|
|
|
|
|
|
Rank: Administration
Groups: Registered, Administrators Posts: 498  Location: Byron Bay Was thanked: 19 time(s) in 19 post(s)
|
As of version 4.3.27 when ESdat is closing it will automatically create a zip file of the database (Access versions) in the same folder as the database file. The database can be recovered from the zip file if this problem occurs again. If you have experienced this problem before I would recommend updating to 4.3.27 or subsequent versions, just to be safe. Warwick
|
|
|
|
|
|
ESdat Forums
»
Forums
»
ESdat
»
23280 unrecognised database format
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.