Front End/Back End

[Garret]

I thought that all modules run automatically when the program starts,
no? If not, how do I run the code?

 

[Rick Brandt]

I thought that all modules run automatically when the program starts,
no?

No. Modules are where you create custom code to "do stuff". It wouldn't
make much sense for all of the "stuff" to just fire off every time you open
your file.

If not, how do I run the code?

In a module you have functions and subs. The code you downloaded consists
of two functions. On ethat creates and sets a custom databse property and
one that does the same thing in a manner such that only users with
Administer authority on the database can change the settings on that
property once it is set.

 

[Garret]

No. Modules are where you create custom code to "do stuff". It wouldn't
make much sense for all of the "stuff" to just fire off every time you open
your file.

I usually declare global variables in there, so I thought the code runs
at startup so that all the variables are created as soon as possible to
be used anywhere.

In a module you have functions and subs. The code you downloaded consists
of two functions. On ethat creates and sets a custom databse property and
one that does the same thing in a manner such that only users with
Administer authority on the database can change the settings on that
property once it is set.

Right, but how do I get these functions to fire off like you said?

 

[garret]

I've read some Microsoft help sites, and they say to insert some of the
code in a commandbutton's click event to get it to fire off, is this
what you had in mind also?