Variables, Forms, Tables

[Bryan Hughes]

Hello,

I currently have a split access 2003 .mdb. The (BE) is on my network file
server, this will eventually be upgraded to a SQL server.
When the (FE) is opened several temp tables are created in a temp .mdb in
the local folder.

One temp table holds current user info (this info never changes while the
user is logged in).

Temp table two holds (Selected Case Manager id, Name), this changes when
user selects new case manger from tree menu.

Temp table three holds (CaseFile id, Case Name), this changes when the user
selects another case file from a tree menu.

Temp table four holds (Client ID, Client Name), this again changes when user
selects a client in the case file tree menu.

This data is used to retrieve data from the (BE), and perform other
functions depending on user selection.

This temp temp.mdb is deleted on close.

Is there a better way to do this then using temp tables?

Would a Property Get, and Let statement do the same thing better, or should
I use a hidden unbound form hold the info?

-TFTH
Bryan

 

[Allen Browne]

A hidden unbound form is a very simple solution, and its Unload event can
also act as a quazi-"Application.Close" event.

Unlike a global variable, the unbound form does not lose its values when you
reset the program (during development). And it is much faster to retrieve
the values from the form than to DLookup() a value in a table.

If you have just a few values like that, and you need to retain them between
sessions (i.e. after Access closes), you could just use temp tables in the
front end. For data of that size, you won't really bloat the front end, and
it's simpler and quicker than creating databases and attached tables and
then destroying them again.

Of course, there is no "right" answer: whatever is simplest is best.