Use of public variables with a multi-user database

[John S. Ford, MD]

I'm not really sure how to ask this. I'm developing an Access 97 database
which will ultimately be put on a central server with access to it on many
workstations. The "back end" will reside on the server with the "front end"
(forms and reports) on the workstations.

One of the forms transmits some information to a report (WHERE filter) and
some data for the report's title page using public variables residing in a
separate module. This works perfectly right now if I'm the only user of the
database. (It hasn't been deployed yet.)

My question is this: When it IS deployed, are there going to be problems
with multiple users relying on the same public variables at the same time
(thus creating confusing reports) or is there a way of making them public
ONLY within a given workstation?

I understand that public variables pose a problem where the goal is
"encapsulation" but I haven't yet figured out how to get around this.

John

 

[Douglas J. Steele]

Since the modules and forms are all in the front-end, and each user has his
or her own copy of the front-end, there won't be any problem.

 

[John S. Ford, MD]

Well that's great then! Thanks, I needed that!

John