Split Database

[smikkelsen]

Quick question on split database design/maintenance.



I have a database on a network with 7 or 8 users accessing it, sometimes all at once. I know the correct thing to do is split the database, and have alll the forms, etc. on front end, but I have been reluctant to do so because i don't know a lot about it. I can only find some general info on it, so if someone can offer their suggestions, I would be very greatful.

When I split it using the wizzard, it will save the back end where I designate. Then, if I move the front end, or the backend at any time, is there one central location that I can go in and update the path? For example, right now I am still making daily updates, and changes to the database. I would like to be able to use version numbers once it is split so my users can copy the new front end to their computer from time to time. How does this work exactly? And like I said, if I ever need to change the location of the backend, is the database worthless then since it is split already? or can I somehow update the path in one place?

And if I ever need to combine the database again, is that possible?

Thanks

[Avelino Sampaio]

Hi

Do a test on your network, using of the example below.

http://www.access-programmers.co.uk/...d.php?t=191306

[RuralGuy]

There are at least a couple of free utilities that automate installing updated FrontEnds to the user's PC.
http://www.autofeupdater.com/
http://www.btabdevelopment.com/main/...8/Default.aspx

[smikkelsen]

Thank you, those were all very helpful. Although the one basically said you can use to test for free, but to put on your server was 175 bucks. NOt sure if I misunderstood that or not.

Anyway, thank you all for the info, I have things split and running smoothly now. Its much easier to make db changes and push a new version with a local front end on each machine.

[RuralGuy]

That's great! I know you will find it much easier to maintain your system.