Discussion Locked

MS Access 2000

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm in the process of creating a database at work... the first one I've made that others will use. There will be no more then 10 users and we do not have a programmer version. So far I have set up the database with a password on the server. I've set up a database on each of two users pcs, linked only the tables they need and imported the queries, forms and reports they need. Then set up each with their own switchboard. Is this the best way to set up with the version we have? Before I started creating this database the company had someone else, who knew less about Access then I, create one and the database became corrupt twice. He had tables set up without primary keys and had users inputting data directly into tables. Of course I want to do the best job I can, but I want to set it up with as much safety as possible. I won't be there too much long, but I want to leave them with something that works.
So... I'm open to suggestions and thank you in advance for your time and attention.
debbie

5 replies

by donq

It sounds as though you are on the right track. The BEST thing you recognize it the requirement to populate your Forms and Reports with a query. I populate everything (including Combo boxes, etc.) with a query to insure users always have the latest data AND programmers have the greatest flexibility.

Unless you are very experienced the database password is as much security as you want to attempt, however your need to create unique user PC links is a little strange - but if it works????

Ihave been doing Access since it came out in 1993 and you sound as though you have a good grip on its capabilities, limitations, etc. so my only suggestion would be to continue operating as you are and enjoy your successes. Access is extremely powerful and a wonderful product Microsoft has continued to support up to this point (lucky 4 us!)

Don Quigg

by fschmude

Hello Debbie,

make sure you execute the feature "compact and repair" of Access2000 on all databases in use.

Separating an application in two databases (1 holds the tables, 1 everything else with *linked* tables, users only get the second mdb-file) is a good idea and the way to go.
The file with the tables must be backed up regularly.

HTH

Fritz

This discussion is closed to new replies.