splitting a database, where question

I have built a small but useful database on my own work pc, and now need
to split it for other users. So I wondered if it was best to split it on
my own machine then place the BE on the server, then copy the front end
to local machines.
OR, place the whole unsplit database on the server, then split it, and
copy the front end from the server to local machines.

Thanks

On Sat, 21 Nov 2009 16:25:38 +0000, Bob H wrote:

I would first make a backup.
Then copy my db to the server.
Then on my workstation's version delete all the tables.
Then use the Import feature to link to the tables on the server.
Then on the server remove all objects but the tables.
Done.

-Tom.
Microsoft Access MVP



I have built a small but useful database on my own work pc, and now need
to split it for other users. So I wondered if it was best to split it on
my own machine then place the BE on the server, then copy the front end
to local machines.
OR, place the whole unsplit database on the server, then split it, and
copy the front end from the server to local machines.

Thanks

Thanks for that, just to be sure, when you say 'use the import feature
to link to tables on the server, in Access 2007, is that 'Link to the
data source' option for tables.

Thanks

Tom van Stiphout wrote:
On Sat, 21 Nov 2009 16:25:38 +0000, Bob H wrote:

I would first make a backup.
Then copy my db to the server.
Then on my workstation's version delete all the tables.
Then use the Import feature to link to the tables on the server.
Then on the server remove all objects but the tables.
Done.

-Tom.
Microsoft Access MVP



I have built a small but useful database on my own work pc, and now need
to split it for other users. So I wondered if it was best to split it on
my own machine then place the BE on the server, then copy the front end
to local machines.
OR, place the whole unsplit database on the server, then split it, and
copy the front end from the server to local machines.

Thanks

On Sat, 21 Nov 2009 17:07:00 +0000, Bob H wrote:

Correct.
-Tom.


Thanks for that, just to be sure, when you say 'use the import feature
to link to tables on the server, in Access 2007, is that 'Link to the
data source' option for tables.

Thanks

Tom van Stiphout wrote:
On Sat, 21 Nov 2009 16:25:38 +0000, Bob H wrote:

I would first make a backup.
Then copy my db to the server.
Then on my workstation's version delete all the tables.
Then use the Import feature to link to the tables on the server.
Then on the server remove all objects but the tables.
Done.

-Tom.
Microsoft Access MVP



I have built a small but useful database on my own work pc, and now need
to split it for other users. So I wondered if it was best to split it on
my own machine then place the BE on the server, then copy the front end
to local machines.
OR, place the whole unsplit database on the server, then split it, and
copy the front end from the server to local machines.

Thanks

Bob H wrote:

then copy the front end to local machines.

See the free Auto FE Updater utility at http://www.autofeupdater.com
to keep the FE on each PC up to date.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a free, convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/