Multi-Users

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a single (not front end/back end) financial database application that
is menu driven. The program operates using financial periods of 1, 2 and 3
....etc for Jan, Feb, and Mar. The "Current Periiod" is stored in a one
record table called tblCurrPeriod.

This period table is used as a filter for all of the transactions and reports.

The problem arises when there are multiple users and one of the users
changes the period from the current period to a different period. This
filter change occurs under the radar and adversely affects the unsuspecting
users who believe that they are still in the current period.

How can I redesign the database filter system to allow different users to
filter on different periods simultaneously?

Many Thanks

Ross
 
Ross said:
I have a single (not front end/back end) financial database application that
is menu driven. The program operates using financial periods of 1, 2 and 3
...etc for Jan, Feb, and Mar. The "Current Periiod" is stored in a one
record table called tblCurrPeriod.

This period table is used as a filter for all of the transactions and reports.

The problem arises when there are multiple users and one of the users
changes the period from the current period to a different period. This
filter change occurs under the radar and adversely affects the unsuspecting
users who believe that they are still in the current period.

How can I redesign the database filter system to allow different users to
filter on different periods simultaneously?

Many Thanks

Ross
Click to expand...

I think you already know one answer to the question, and that is to
split the database. However, since you posted that it's not split, I'm
going to assume that you can't/don't want to split it.

So what you're going to need to do is to change the way you're storing
the value in tblCurrPeriod. Rather than just storing the period #,
you're going to store something to identify the user that put it there.

You can store the username, and id, or something, and then return their
value when you need to know what period it is.

Lots of ways to do this. 1) Access Security 2) Get Username via API
function 3) Let the user pick their own name when starting the database,
and track who they are internally 4) Let the user pick their name when
setting the period 5) Automatically increment/assign the 'userid' when
the database opens based on what values are already in use on the table,
and then remove that 'userid' when they close the database.

-D
 
Duncan,

You are correct on all accounts. I know that I can split the db but, don't
want to.

Thank you for you suggestions.

I think that I could use the user name and the period to uniquely store the
period filter and then uniquely retrieve it (the period).

Thanks again,

Ross
 
Back
Top