Split the Database and VBA code issue

[Boon]

Hello,

I am developing a database that at the end will be splitted to back-end and
front-end. I expect to have about 10 users.

I have forms and VBA code behind the form.

My question is that after I split the database, is the form and VBA code
store in the back end or front end? My concern is that I have a variable in
the VBA code that will store a data that is different from user to user. I
would like to know that do I need to create one variable for each user (each
front end)?


Thanks,
Boon

 

[Marshall Barton]

I am developing a database that at the end will be splitted to back-end and
front-end. I expect to have about 10 users.

I have forms and VBA code behind the form.

My question is that after I split the database, is the form and VBA code
store in the back end or front end? My concern is that I have a variable in
the VBA code that will store a data that is different from user to user. I
would like to know that do I need to create one variable for each user (each
front end)?

You can out standard code modules in the back end by
referencing it as a library. However, anything beyond the
basic references can always cause trouble an should be
avoided if there is another way.

All other modules, especially form/report modules, should be
in the front end.

If you can identify a user without using that "variable",
then you can put user specific informnation in a back end
table keyed on the user identifier. OTOH, If the "variable"
is identifiying the specific instance of the front end,
regardless of who is moving the mouse, then a front end
table is appropriate, even if it can be a hassle to update
the front end.