|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
i am a total newbie with access. I am looking to take a database that
someone else made it is on 5 computers individually and split the database
make 1 backend to store all 5 users contacts in. I also want to be able to
fix the forms, add fields etc. The most important thing is as it is a sales
floor i need to be able to keep each persons contacts private from everyone
else. any ideas on the easiest way to do this . Thanks in advance
|
|
"jomara" <u27274[ at ]uwe> wrote in message news:66fb75fc796c7[ at ]uwe...
[Quoted Text] >i am a total newbie with access. I am looking to take a database that
> someone else made it is on 5 computers individually and split the database
> make 1 backend to store all 5 users contacts in.
I have a good starting article on splitting here, it should help you a lot
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
> I also want to be able to
> fix the forms, add fields etc.
When you split, then you can well do the above. you are "free" to work on
the next great version of your software, or just fix up some things while
everyone is happy working away.....
> The most important thing is as it is a sales
> floor i need to be able to keep each persons contacts private from
> everyone
> else. any ideas on the easiest way to do this . Thanks in advance
Hum, now, the above is something that database systems are not really great
at. I mean, when you walk up to get your car license renewed, any person at
the available desks can bring up your information, and process your new
license using their motor vehicular registration system (which by the way is
a database).
The same goes for processing customer orders, or whatever. the stack of
orders can be distributed to all of the workers in the eh office, and ANY
WORKER can bring up the customer information, and then process the order.
So, as you can see, in 99.99% of cases, a database system GREAT FEATURE is
that any user of the system can bring up customer information etc and work
on it.
When you try build a database that says that all of this wonderful
information is NOT to be shared, then you kind of hit a snag, as that
something database don't do very well.
I suppose the approach would be to save the user name with each record, and
then filter the forms by that particular record, but it hardly going to be
secure, and preventing others from browsing, or brining up information
entered by others is not that easy to do. I suppose in the case of looking
up a sales order, then the fact that someone else in the office made the
order is not a big deal. However, if you are looking to build something that
keeps each persons information separate, but SHARE the same database, then
you will have to write quite a bit of code to handle this. There is not
much advice I can give on this issue, except that databases don't keep data
in the system "separate" very well, and the whole idea of a database is to
EASILY work with large amounts of data as one set of data.
I have written a good many number of systems that track salesperson orders.
Each sales rep can view/filter their own records, and also view others
peoples records too. Not much of a problem, and if someone is sick, or on
holidays, then obviously if others in the building could not use/access that
information, then you really would have a difficult system to use. If you
need to keep senstivite informaton in the SAME database, but not allow each
user to see others informaton, you will find this a lot of work.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal[ at ]msn.com
|
|
|