Split Database

[EasyOnly]

I have a database that I am about to split to the users. But I have obe concern, If I need to add new fields to the table and then to the forms, do I need to go back and re install the new front end to all users again?

Or should I split the database and put both front end and back end in the shared drive?

 

[danvlas]

It's usually better to place a copy of the front end on each client computer. But you can write a batch file to automatically copy the file from the server, then open it.


Daniel Vlas
Systems Consultant

 

[TheAceMan1]

How are ya EasyOnly . . .

[blue]I have a database that I am about to split to the users.[/blue]

[ol][li][blue]BackEnd[/blue] resides on the server or a common location to all users.[/li]
[li][blue]FrontEnd[/blue] is distributed [blue]local[/blue] to all users.[/li][/ol]

[blue]If I need to add new fields to the table and then to the forms . . .[/blue]

Make [blue]table changes[/blue] to the backend before you [blue]update forms[/blue] in a frontend master copy. Then distribute the master . . .

See Ya! . . . . . .

Be sure to see thread181-473997 [blue]Worthy Reading![/blue]
Also faq181-2886 [blue]Worthy Reading![/blue]

 

[missinglinq]

You absolutely have to place the front end on each user's PC, not on a shared drive, with only the back end on the shared drive.

Obviously, to add fields to your tables you're going to have to have exclusive access to the back end while you're doing this, in order to not lose data.

Tony Toews has an excellent hack that's designed to do all the heavy lifting involved in distributing modified/updated front ends. He also gives an excellent overall picture of split databases, and the best thing of all, it's free!

http://www.granite.ab.ca/access/autofe.htm

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!

 

[missinglinq]

Forgot to add, before you do anything, backup you database!

The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!