How to use different data sets with the same database structure?

[sturose2000]

Hello, I've got a pretty general question but I'll try to relate it to a few
specific situations.

*Is it possible to design the structure (i.e. the fields in my tables, the
layout of forms, the queries, etc.) of my database, then selectively "load"
one or more data sets when I open it?*

For example, if I want to build a fitness-tracker, can Mom, Dad, Brother,
and Sister all have his/her own data file? When one person opens the
application, s/he can look only at her/his history....Or, another example,
if I want a copy of the "empty database shell" to give to members of a club,
so that each member can track in an individual file his/her collection of
trinkets relating to the club....

If someone could please point me in the right direction (even simply the
name of a function/operation to do something like this)....Also, if there is
no easy way to accomplish this per se, can you please recommend some kind of
workaround (for example, should I have "duplicate" tables of identical
structure but holding data for each individual user, or should I keep all
the data together and use a switchboard on open to only use one user's data,
etc.)

Thanks in advance,
Stu

 

[Tom Lake]

Hello, I've got a pretty general question but I'll try to relate it to a

few specific situations.

For example, if I want to build a fitness-tracker, can Mom, Dad, Brother,
and Sister all have his/her own data file? When one person opens the
application, s/he can look only at her/his history....Or, another example,
if I want a copy of the "empty database shell" to give to members of a
club, so that each member can track in an individual file his/her
collection of trinkets relating to the club....

You can store all the data in a single table and add a field to identify the
person (initials, maybe?). On the startup form, put a text box to allow
input of the name. Base all further forms on a query that has that name as
a criterion.

Tom Lake

 

[George Nicholson]

Yes

Split your database into BackEnd (tables only) and Backend (everything
else).
Make copies of the backend for MomsData, DadsData, etc.
Using LinkedTableManager (or a variation of the code at
http://www.mvps.org/access/tables/tbl0009.htm ), you can link the FE to the
desired BE at startup, or on demand.

Another approach would be to design your tables and queries with an
additional field, "UserName", and capture who the User is at startup. Then
have everything simply present "their" data.