tables saved in separate database

[Carrie]

I have designed a database which several users will be
using to enter information into various forms and then
print reports. I was told that I should save my tables in
one database and my forms/reports in another database that
the users will access (to prevent corruption). I've never
done it this way before and just wanted to confirm that
this is the best way to do it. I'm assuming I would save
it twice and delete the tables in the shared database and
import them from the other database - is that right, and
do they need to be on separate drives?

Also, if this is correct, will I have any trouble
importing additional forms later?

Thanks so much!

 

[Immanuel Sibero]

Hi
See my inline comments

Immanuel Sibero

I have designed a database which several users will be
using to enter information into various forms and then
print reports. I was told that I should save my tables in
one database and my forms/reports in another database that
the users will access (to prevent corruption). I've never

Yes, this is the "split database" design. If you search Google on "split
database", there's plenty of info on the merits, and advantages. Minimizing
corruption is just one of them. The database containing your tables is
referred to as the Backend. The database containing forms, reports, queries
etc. is referred to as the Front End.

done it this way before and just wanted to confirm that
this is the best way to do it. I'm assuming I would save
it twice and delete the tables in the shared database and
import them from the other database - is that right, and
do they need to be on separate drives?

Saving the database twice is correct.... well, more like making two exact
copies of the database, so now you would have two identical databases.
Delete the tables from one of them, this will be your Front End. On the
other copy, delete everything but the tables, this will be your BackEnd.
Place the Backend on a shared drive (i.e. network share) where all your
users have read/write access. Link all the tables in the Backend to the
Frontend. At this time, you may distribute multiple copies of the Frontend
to your users.

NOTE: As always, make good backup of your database before doing anything
this nature.

Also, if this is correct, will I have any trouble
importing additional forms later?

No. If you add new forms, queries, reports, or change the program; you would
do this on the Frontend. Once your done, distribute them to your users. Your
users would simply replace their copy of the Frontend with your revised
copy.

Thanks so much!

NOTE:
As a final note, the above should be taken as a general guideline, if you
havent "split a database" before, I encourage you to search for information
detailing the specific steps. www.microsoft.com or www.google.com both have
excellent information on this. It's not that complicated but it's worth it.

 

[Kevin3NF]

Also, See tools>>Database Utilities>>Database Splitter for a very convenient
wizard to get you started

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com/NewsGroups.htm