Can Autoexec be made not overwriteable ??

[Jay]

I have a database that has an autoexec macro and has the shift key down
get-around disabled
Is there anyway to make the autoexec not overwritable - ie if someone
exports another autoexec to the database - the original one will not be
overwritten??

 

[Steve Schapel]

Jay,

I was not aware that it was possible to export another Autoexec to the
database. Certainly you can *import* another autoexec into the
database... but then that pre-supposes you already have design access to
it. I assume you are meaning that if this happened, it would be for
malicious purpose. I suppose if you really think there is a danger of
this occurring, there would be various steps you could take to minimise
the likelihood. One such would be to forget the idea of an Autoexec
macro altogether, and instead use some code on the Opne event of a
startup form, to do the same thing as the Autoexec does currently. If
you then deploy the application as an MDE, it makes it pretty hard for
anyone to mess with.

 

[Jay]

Steve

the auoexec runs code that closes the database off so that users cannot
access design view - with all of these start-up settings changed - you can
still export a blank auotexec - or an autoexec that reverses all of these
settings into the database

Unfotunately - we cannot mde it as the database does some form re-design
depending on run-time options chosen by the user

I think that even if the code was entered into a form that was selected as
the start-up form - this setting could be amended by an imported autoexec

Don't think there is actually a way around this! - but you never know...

 

[Steve Schapel]

Jay,

It would appear that there are a number of significant design flaws in
this application.

And I still don't understand your purpose in asking this question. What
are you trying to protect against? If someone is trying to make
unauthorised changes to your software, I suggest referring to the police.