[AccessD] Naming Convention (Query SQL correct but notvisibleindesign view)

Hi William

At lunch, sorry launch time, if you check the references and one is
missing and you get it reestablished, your code is left uncompiled. Your
code cannot compile itself, thus you'll need to do that from the
"outside" and - seen from the code's view - a macro is such an outside
place. Another outside place place is a form with a timer event.

As the AutoExec macro will run before anything else, you can let it
first check and repair the references, then - if needed - recompile the
app; it only takes a few seconds. 

/gustav

>>> dejpolsys at hotmail.com 28-12-2004 16:29:07 >>>
"From a macro you can recompile your code after adjusting the
references." gustav

..ok ...I'm confused ...why would I want to use a macro to do that?

William Hindman


----- Original Message ----- 
From: "Gustav Brock" <Gustav at cactus.dk>
To: <accessd at databaseadvisors.com>
Sent: Tuesday, December 28, 2004 9:52 AM
Subject: RE: [AccessD] Naming Convention (Query SQL correct but
notvisible 
indesign view)


> Hi Dan
>
>>From a macro you can recompile your code after adjusting the
> references.
> I have found no other way to do that (and no, the
> SysCmd(SomeCompileConstant) doesn't work except when run from the
debug
> window).
>
> /gustav
>
>>>> dwaters at usinternet.com 28-12-2004 15:30:28 >>>
>
> You said you use an autoexec macro (I've never used macros in
Access).
> I use an invisible startup form, which calls a list of procedures
and
> functions in a standard module.  Do you know of an advantage one way
or
> the other?