Access2003

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

Guest

Currently we run Access 2003 on several machines on XP pro machines networked
with Microsoft Networking.

All the tables are in a separate and central database on a LINUX server. The
application is running on each individual machine with the tables linked to
it.

Is it possible to have users log on and to be able to track who does what to
the data in the central tables? I'm a bit concerned that if I let everybody
run the same application, shared, from the server it would create too much
network traffic and slow everything down. We have 2 or 3 regular users and
another 4 or 5 occassional users who could also just look at the data without
being able to change things. Total network at present is 16 machines, about
half of them laptops.

Any advise would be very much appreciated.
 
The number of users should present no problem at all, assuming 100Mb
Ethernet wires (no unstable connections such as WiFi).

You can log users in by specifying a startup form (Tools | Startup), and
using its Open event to insert a record into your logging table. This link
will give you the name of the computer:
http://www.mvps.org/access/api/api0009.htm
or if you prefer the network user name:
http://www.mvps.org/access/api/api0008.htm
If you want to log users out, open a hidden form, and use its Unload event,
since there is no Application Close event.

If you want to create a log of all inserts, deletions, and edits, see:
http://members.iinet.net.au/~allenbrowne/AppAudit.html
 
Thanks Allen,
I'll give that a try soon. It took me a while to find my post and your
answer to it again. I knew that I had posted my question but could not find
it because the listings are not sorted by date.

I found it eventually after realising that the posting date had no relevance
to the position in the list.
 
Hi Allen,
I presume you suggest that I consolidate the data base into a security
enabled one and do away with the front end / back end design. Is that
correct?
Can I follow your suggestions on a front end / back end design also? If yes,
the log tables would have to live on the respective users PC, right?
Please advise.
 
There is no problem with the front end/back end design.

If the back end table are Access mdb files, then I see no reason why all the
tables should not be in the one mdb file (unless the file is more than 1GB
in size).

You can run Access security (mdw file) if you wish, and then use
CurrentUser() for the logging purposes. But if you do not need that
security, you could just log the users by their Windows user name or
computer name, using the API calls in the links.

Personally, I would put the log table in the back end.

Please post back again if that is not clear.
 
Now I have (or seem to have) another problem. I use the MS Switchboard
manager and the switchboard is the startup form. Of course it has already an
event procedure for the open event. How do I incorporate the new code? Do I
copy it into the procedure called by the Open event?

Please advise
 
You cannot have two Form_Open procedures in the one form.
Just add the code into the existing procedure.

Or, rename the procedure to say "LogIn", and in Form_Open:
Call LogIn()
 
Question: I have installed Access2003 on WinXP with workgroup pier to pier
situation. While I do most of the data entry, and the attorneys are mapped to
my computer when they want to access Access, how do I setup the workgroup so
each attorney may take advantage of such objects as ActionItem/Calendar, etc.?
Appreciate input. Thanks.
Joan
 
Back
Top