Autoexec Macro in Access 2000

[Antonio via AccessMonster.com]

Hello,

I've developed a database in A2003 and installed it in a PC running A2K.
The database is split in 2, one for F.E. and another containing the tables as
the B.E.
Also, I have an MDW file which secures all the objects, granting levels of
security to the several users.

Works swift in A2003, but when I try to open it in A2K, problem starts right
at the beginning.
The Autoexec Macro is setup so that it runs a piece of validation code and
then it just has to open a form. But it just Halts when opening the form and
it crashes Access.

1) Does the Autoexec Macro need to have permissions?
2) Does the Module where the code is need to have permissions?
3) Where in A2K can I change the level of security of Macros?

Besides this, is there any more details that I should look at?

Thanks a lot

Antonio

 

[Craig Alexander Morrison]

Personally I would lose the Macro set a form as your StartUp Form to kick
your application into life, see menu Tools, Startup.

As to security, permissions etc you may get better and fuller answers in the
m.p.a.security newsgroup.

 

[Antonio via AccessMonster.com]

Thanks,

I have to use the Autoexec because the first thing I want to run is a
validation code. Depending on that validation (by time, 30 days trial period),
Access either opens a Form or kicks the User out.

I wouldn't want to trigger this event on the Form itself, I would like to do
it before opening it. Hence the startup...

Antonio

Craig Alexander Morrison wrote:
Personally I would lose the Macro set a form as your StartUp Form to kick
your application into life, see menu Tools, Startup.

As to security, permissions etc you may get better and fuller answers in the
m.p.a.security newsgroup.

Hello,

[quoted text clipped - 22 lines]

Antonio

 

[Craig Alexander Morrison]

No, the StartUp form is the place for this.

Indeed in some of my applications the StartUp form is a single pixel in size
and immediately passes control on its OnOpen event to the necessary Licence
and Expiry checks.

Macros are much easier to break.

--
Slainte

Craig Alexander Morrison
Crawbridge Data (Scotland) Limited

Thanks,

I have to use the Autoexec because the first thing I want to run is a
validation code. Depending on that validation (by time, 30 days trial
period),
Access either opens a Form or kicks the User out.

I wouldn't want to trigger this event on the Form itself, I would like to
do
it before opening it. Hence the startup...

Antonio

Craig Alexander Morrison wrote:
Personally I would lose the Macro set a form as your StartUp Form to kick
your application into life, see menu Tools, Startup.

As to security, permissions etc you may get better and fuller answers in
the
m.p.a.security newsgroup.

Hello,

[quoted text clipped - 22 lines]

Antonio

 

[Craig Alexander Morrison]

I should also point out that the StartUp form loads and processes well
before the AutoExec is even considered for execution.

I added an autoexec macro to one of our formal startup routines and two
dialog boxes appeared both had to be cleared in turn before anything else
happened only when the custom logon screen appeared did the autoexec
function and only then to display a message box.

The startup code checked for a Licence an Expiry Date the Edition of the
software, that all tables were linked that the structure of the database
matched the version of the application etc etc all before the autoexec had
even been woken up nevermind getting out of bed .

This is with Access 2003 which I believe you are using.

Basic message is - avoid macros they have not been removed from the product
for backwards compatibility reasons only.

--
Slainte

Craig Alexander Morrison
Crawbridge Data (Scotland) Limited

Thanks,

I have to use the Autoexec because the first thing I want to run is a
validation code. Depending on that validation (by time, 30 days trial
period),
Access either opens a Form or kicks the User out.

I wouldn't want to trigger this event on the Form itself, I would like to
do
it before opening it. Hence the startup...

Antonio

Craig Alexander Morrison wrote:
Personally I would lose the Macro set a form as your StartUp Form to kick
your application into life, see menu Tools, Startup.

As to security, permissions etc you may get better and fuller answers in
the
m.p.a.security newsgroup.

Hello,

[quoted text clipped - 22 lines]

Antonio

 

[Antonio via AccessMonster.com]

Thanks Craig, I'll try it in the OnOpen event of the Startup Form.

Antonio

Craig Alexander Morrison wrote:
No, the StartUp form is the place for this.

Indeed in some of my applications the StartUp form is a single pixel in size
and immediately passes control on its OnOpen event to the necessary Licence
and Expiry checks.

Macros are much easier to break.

Thanks,

[quoted text clipped - 22 lines]