Question Access can't delete Datebase After compacting it

[R_J_Potter@msn.com]

Microsoft Access can't delete c:\....\MyDatabaseName.accdb after compacting it. The compacted database has been named c:\....\Database1.mdb.
Database has been setup to "Compact on Close" under Options for the current database.
My Application has operated flawlessly for nearly 8 years and all of a sudden occured 4 times this month.
The database is not in read only status.
The original database is deleted.
I have to open "Database1.mdb", Save it as "MyDatabaseName.accdb"
I do not know what is really causing this problem.
My Operating System is Window7 Professional w/16GB memory and "Microsoft Office Professional 2010"

 

[bob fitz]

I would turn off the "Compact on Close" under Options. I believe that this feature can cause corruption problems. Google "Compact on Close".
Here are a couple of links on the subject: http://allenbrowne.com/bug-DeleteOnCompact.html and http://rogersaccessblog.blogspot.co.uk/2010/12/should-i-use-compact-on-close-feature.html

 

[RainLover]

Place a copy of the original in a different folder. Then do a compact and repair on the new copy. Does this now work.

I would also agree with Bob. My suggestion is to help find the problem.

 

[R_J_Potter@msn.com]

I've taken your suggestion and turned off the "Compact on Close" under Current Database Options. I am considering splitting this application as data files grow daily.
I routinely back-up all the files in my Documents Folder, C:\ApplDocs, Pictures and Videos...
I still don't know what caused those 4 errors. I'll probably never know...
Ron

 

[RainLover]

Rod

The Standard approach with any commercial database, no matter how small it is or how few users you have is to split the database with the Backend placed on the server. This allows current users to continue using it while you continue to develop. As you feel fit you can replace the front end with the latest improvements.

While Backend belongs on the server where it can be accessed by all users and easily backed up along with your normal back up routines. The front end resides on the client’s machine and is not shared.

You should also use separate Databases for development. Back up regularly. Many times a day.


Why is your database growing on a daily basis? Is this a big increase? If you think your Backend will grow to 2 Gig we had better have a closer look as this is the limit allowed.