Back End Blowing Up - URGENT

[nashat21]

Hi there..

A few months ago we were having major problems with our database becoming an unrecognized database format, etc.. The majority of suggestions from this forum were to split the db into a front end and back end.. i did that and it has worked very very well for us - thank you! however, in the past week or so, the back end seems to "blow up" (unrecognized database format) almost daily towards the end of the day. i have been able to succesfully compact and repair and the one obvious thing that i notice is a record full of ###### signs in one or more tables. today however, i haven't been able to compact and repair and the repair utility stops responding or MSACCESS.exe makes a fatal error and everything shuts down. I'm compacting and repairing as I type so any immediate help would be greatly appreciate (all other types/forms of advice also welcome

Nashat

 

[Autoeng]

Try creating a new database which will become your new back end. Import all of the tables from your original back end into the new one. Access tries to correct errors on import and hopefully will with your application. Look through the imported tables and delete any problem records that you find. Save the old back end other another name and then rename you new back end to the appropriate name.

Hope this helps.

Autoeng

 

[nashat21]

thanks for the reply..

unfortunately, i cannot get to the tables in the backend to be able to import or manipulate them in any way..

any other ideas?

nashat

 

[Autoeng]

From the back end database window can you right click on on your table and export it to an empty database or an excel file? Can you even open your backend? (that sounds bad, doesn't it?).

Autoeng

 

[nashat21]

can't even open the back end!!!!!!!!!!!! i even tried Microsoft's Jet Compact Utility.. no luck!

Nashat

 

[Idjit]

When you launch Access, if you click on "Help" there's an option "Detect and Repair...". This utility repairs all office files. Does anyone know if this might help solve Nashat's problem??

 

[Jeff Bailey]

Are you using A97? If so, you might try opening the BE using A2K and selecting the Convert option. Repair the converted database and export as 'Earlier Version' (i.e. A97). This has saved a couple of clients when all seemed lost ...

There are professional data recovery services available which could very likely restore most or all of your data if necessary.

BACKUP, BACKUP, BACKUP!!!

Jeff.

 

[nashat21]

hi again..

thanks for the tip, but our db was in A2K.. but ihad backed up so I had ultimately convert to yesterday morning's version of the db so in effect we lost a day's worth of work.. oh well.. but thanks for all your help!

nashat