How early can I turn warnings off?

[AlexCuse]

I have tried running an autoexec macro and a separate autoexec macro to run code to turn warnings off. I have an application published through Citrix Server that allows the user to write to one table from a form. Every other table they are not allowed to write to, because they do not have access to the folder on Citrix Server where the app resides. The table that they need to write to is stored in an accessible folder.

My question is, how can I turn warnings off early enough so that the read only warning does not come up when the user opens the app? The traditional methods don't seem to be working.

Thanks a lot,

Alex

 

[Crowley16]

you can turn warnings off as soon as you start the database, although I wouldn't recommend this...

personally I wouldn't use macros at all, that way I can have error handling, and have the warnings turn off just before the relevant operation and turn it back on after...

--------------------
Procrastinate Now!

 

[AlexCuse]

My problem is that I need to turn warning off before access starts the database to avoid the 'Read Only' warning. I want to disable warnings and then turn them back on when the form comes up and gets the focus, but using autoexec I have not been able to get warnings off until after I get the 'Read Only' warning. Is there any way to set the default for warnings to 'off' in just this particular database, and then enable shortly after startup?

Thanks a lot,

Alex

 

[Crowley16]

in that case, you'll have to see if any of the command line arguments cover this...

I suggest the read only flag, /ro as the mostly likely candidate...

--------------------
Procrastinate Now!

 

[AlexCuse]

Won't /ro actually open the database as read only though? I need users to be able to write to 1 table. The only reason I'm worried is because I don't want people constantly calling me saying "it only opens as read only" all day.