Re: Autoexec Macro in Access 2000

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
"Antonio via AccessMonster.com" <u11740@uwe> wrote in message
news:5a4b8c22204a0@xxxxxx
> 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
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/Forums.aspx/access-conversion/200601/1


.

Relevant Pages

  • Re: Autoexec Macro in Access 2000
    ... validation code. ... Access either opens a Form or kicks the User out. ... Hence the startup... ... Antonio ...
    (microsoft.public.access.conversion)
  • Re: Autoexec Macro in Access 2000
    ... I'll try it in the OnOpen event of the Startup Form. ... Antonio ... >Craig Alexander Morrison wrote: ...
    (microsoft.public.access.conversion)
Loading