Splitting Database

[Shadab Kamal]

Re: https://www.accessforums.net/tutoria...ent-20306.html
I found the Dec 2011 post on splitting an Access database really helpful. I created a database for my office that has become increasingly complex & now has 10's of thousands of records in it in
several tables. It is set up as a multi-user database, but it is not split and not surprisingly, performance is getting worse & worse & we have had several corruption issues. It sounds like I need to split it for sure.



My question is (& I couldn't find anything that addresses this), if each of my users (about 8-10) has a local FE on their machine, what happens when I create new queries, need to update forms, etc? Does this just happen on my local copy & then I need to copy it to each users computer? This DB has been a very dynamic tool & I don't expect that to change any time soon & I am concerned about the technical issues that regular updates to the front-end might cause.



_________________
Johni Imtiaz..!!

[June7]

You must provide users with an updated version of the frontend, just like getting a new version of any software application. Review https://www.accessforums.net/code-re...end-33331.html

A properly designed db should seldom require modification once it is matured beyond beta stage. If your db design is still in constant revision, I suspect something is wrong with structure.

[NTC]

Yes; exactly correct: it just happens on your local copy & then you need to copy it to each user's computer