[AccessD] Separate mdb for housing temp tables

On 24 Aug 2006 at 20:23, William Hindman wrote:

> "Note that if you do not create objects or write to internal tables in your 
> frontend database, you may be able to write protect the frontend file 
> itself. That frees you from any corruption or bloat." /gustav
> 

I've just had a problem with this.

I've got an A2K application (developed in A2K mode on  an A2K2 
installation) that runs 
startup code from an Autoexec macro, including opening the initial menu 
form.

If the mdb is RO, it doesn't execute the macro on A2K so the user just just 
see a blank 
window with no menu. It works fine under A2K2.

Opening the database window and trying to run the macro gives a 
message:

"Microsoft can't find the macro Autoexec.
The macro (or it's macro group) doesn't exist, or the macro is new but 
hasn't been 
saved........"


As soon as I remove the RO attribute from the file, it works perfectly under 
both versions.




-- 
Stuart McLachlan