S
Steve
I have a .mdb that I use as a sort of time keeper in my office. It opens
automatically when the user signs in and closes when they log off. The only
thing the db does right now is, when the form opens, it records the logon
time from windows and puts it into a table. And when the form closes
(computer is shut down), it records the time and enters it into a table.
That's all it does. Two events and two append queries per person per day. The
max number of people that will have it "open" at one time is 19, but 80% of
the time only 6 to 10 will have it open. I've been using it for several weeks
this way without a hitch. I guess the relatively low activity of only two
append queries isn't causing a problem. It is not split since there is no
interaction by anyone with it. The only thing that is needed is to open a
form at the beginning of the shift and close the form at the end of the shift
(again, both are done automatically behind the scenes and the user never
interacts with the mdb or even knows it's there).
Here's my question: I am considering having the .mdb also record other
information every minute using the forms OnTimer event. So, every minute, a
procedure will fire and append a new line to a table. I am going to set it up
so I can turn it off and on by person, so I can have as many or as few as I
want having this extra function running as I want. How many people can I
reliably have this extra function running on at one time given what I
described above? I can also have this function run and append the record into
another db that is used less frequently, but I have to run the code in this
db that runs in the background on everyone. Would it be better to insert the
record into the other db that is used much less frequently? I would like to
run this extra operation on everyone at the same time if I can, but if I have
to run it on only a few at a time, I can do that to.
Thanks
Steve
automatically when the user signs in and closes when they log off. The only
thing the db does right now is, when the form opens, it records the logon
time from windows and puts it into a table. And when the form closes
(computer is shut down), it records the time and enters it into a table.
That's all it does. Two events and two append queries per person per day. The
max number of people that will have it "open" at one time is 19, but 80% of
the time only 6 to 10 will have it open. I've been using it for several weeks
this way without a hitch. I guess the relatively low activity of only two
append queries isn't causing a problem. It is not split since there is no
interaction by anyone with it. The only thing that is needed is to open a
form at the beginning of the shift and close the form at the end of the shift
(again, both are done automatically behind the scenes and the user never
interacts with the mdb or even knows it's there).
Here's my question: I am considering having the .mdb also record other
information every minute using the forms OnTimer event. So, every minute, a
procedure will fire and append a new line to a table. I am going to set it up
so I can turn it off and on by person, so I can have as many or as few as I
want having this extra function running as I want. How many people can I
reliably have this extra function running on at one time given what I
described above? I can also have this function run and append the record into
another db that is used less frequently, but I have to run the code in this
db that runs in the background on everyone. Would it be better to insert the
record into the other db that is used much less frequently? I would like to
run this extra operation on everyone at the same time if I can, but if I have
to run it on only a few at a time, I can do that to.
Thanks
Steve