Shared Database Application

  • Thread starter Thread starter Kevin
  • Start date Start date
K

Kevin

A beginning VBA user here. Please forgive the ignorance
here.

I have been asked to put together a shared database
application. It will reside on a server and will be
accessed by various people with access to that server.
These people will be using forms I create, to access data,
modify data and delete data. Two of the same people will
never be alllowed to access the same data, so I dont
anticipate having problems with record locks, etc.

These people will log into this database using a login
routine designed in MS Access. This login information
will dentify who they are and what information they will
have access to from the login information.

-How can i store this data and have it available to my
routines and functions for the user, when they run
reports, queries, etc? If the login data is assigned
Public variables, will it be overwritten by "the next
user" loggin in? I thought of writing identification
information to a switchboard/form and using this
information for reports, queries, etc, but I think that it
will be overwritten by "the next user"....or is the
information contained on the forms, stored locally????

I need some guidance and suggestions please.

Regards
 
If you need security in you application, DON'T write your own. Access has a
security model built into it that, while it may not be perfect, is better
than anything you are likely to come up with. Microsoft has provided a
Security FAQ which answers most of your questions. You can find it here:
http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp
or you can find a hard copy here:
http://rogersaccesslibrary.com/knowledge.html

Read it over several times before trying it and use a COPY of your database
to begin with.

--
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L
 
Kevin,

Since you have a multiuser environment, you will split your database into a
front-end (FE) and back-end (BE). Access provides a function in the Tools
menu to do this and results in a BE that contains the tables and a FE that
contains forms, reports, modules, etc.

A single copy of the BE will be on the server and each user will have a copy
of the FE on their local drive.

This arrangement answers your question about storing user login data. If
you use public variables, each FE will have their own. ALternatively, you
could simply place this data in hidden text controls somewhere in the
application, such as the switchboard form, and achieve the same result.

Tom
 
Back
Top