Thanks Chris,
I followed you suggested solution. All objects were successfully imported
into the new database except the corrupt one. I designed a new form to
replace it. Suddenly, the problem occurred again. Do you have any other
solutions!! The problem often occurs when I do some changed in a text
controls row source or the forms data source.
To prevent this I have to make back up copies every 10 minutes and it’s …
"Chris O'C via AccessMonster.com" skrev:
> While adding more RAM wouldn't hurt, you probably have a corrupt database
> file. Create a new database file and import everything from the current
[quoted text clipped - 14 lines]
> >512 Mb RAM
> >Access 2003 SP3
Chris O'C - 22 Apr 2008 21:02 GMT
Use Marshall's recommendation, decompile. First make a copy of your file and
only work with the copy. Turn off any automatic startups: set the startup
form to none and rename your autoexec macro to something else temporarily.
Now use the /decompile switch in your startup command. I create windows
shortcuts for things like this. Here's an example of the shortcut's target.
(It should be all one line, but change it to match your paths and db name.)
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\database\db.
mdb" /decompile
Double click on the shortcut to decompile. When it's done, compile the code,
then compact/repair. Reset the startup form and autoexec macro to the way
they were. See if that helps.
Chris
Microsoft MVP
>Thanks Chris,
>I followed you suggested solution. All objects were successfully imported
[quoted text clipped - 12 lines]
>> >512 Mb RAM
>> >Access 2003 SP3
Alan - 01 May 2008 07:11 GMT
> Thanks Chris,
> I followed you suggested solution. All objects were successfully imported
[quoted text clipped - 31 lines]
>
> - Show quoted text -
Hi,
You may try Advanced Access Repair at http://www.datanumen.com/aar/
This tool is rather useful in salvaging damaged Access MDB files. Hope
this helps.
Alan