Auto-suppress/click-through Access startup msgs?

[Access9001]

Sometimes when opening an Access db you get an immediate message -- sometimes a fatal error"has occurred during the last usage ("caused a serious error the last time it was opened"), or the message that you get when opening Access for the first time. Is there any way to auto-confirm these things on open or something similar?

 

[ghudson]

Sounds like your database might have some corruption. Have you compacted it lately? Or imported all db objects into a new database? I would fix the problem instead of trying to ignore it.

 

[DCrake]

For a start this lends towards the fact that you have corruption in your mdb. You need to rebuild the app into a fresh one. You should then not any messages.

 

[Access9001]

Yes, plenty of compacting -- but sometimes the errors crop up unexpectedly (via corruption) and we need to fix them appropriately through automation when the databases are run.

 

[DCrake]

Has the database been split? FE/BE?

 

[boblarson]

Sometimes when opening an Access db you get an immediate message -- sometimes a fatal error"has occurred during the last usage ("caused a serious error the last time it was opened"), or the message that you get when opening Access for the first time. Is there any way to auto-confirm these things on open or something similar?

Short answer - NO, there isn't.

 

[Access9001]

Yes -- everything is compacted on close, FE/BE separated. The problem is that people lock up the tables or interfere with compact processes /etc and sometimes the errors crop up and ruin other automations.

 

[DCrake]

I suppose in a single user situation the problem never appears. You may have to revise you code to only activate automated processes if no one else is logged in to the application.

Then again that depends on what is bening performed in your automated processes.

These are known as logical errors, errors that occur due to the way the system code was introduced.

 

[Access9001]

Is there a way to ensure processes only run if one user is involved, and that anyone else who tries gets booted?

 

[DCrake]

There is a sample app that checks who's logged into a database in the samples forum. You could utilise this to see if others are logged in. If so cancel the automated process.

 

[Access9001]

I am unable to find this sample -- where might I locate it?

 

[DCrake]

Follow this link