拆分访问数据库的说明

Question

I've read multiple articles and watched videos but this is a big change to the structure so I want to confirm the idea that I have.

Splitting will separate the tables and forms/queries into separate files. I get that much. But two questions.

1) Should I backup my database beforehand?

2) Can I edit the forms in design/layout view while they're being used by, say, a data entry team?

The issue I'm running into now is that I created a simplistic front end for another team to use but I now need to buff it up while they use it. I heard this was the most efficient way to do so.

Answer 1

1) Yes, of course.

2) Every user should have their own local copy of the frontend.

You develop the new frontend version on your local computer, then when it's ready you put it on a network drive, and everyone gets their new local frontend from there.

Here are some ideas how to automate this: https://stackoverflow.com/a/33782644/3820271

You should never make design changes on a database that other users are currently using. (shudder)

Edit re. comment:

All forms are in the frontend, so yes. You work on your development frontend, connected to a development backend (a copy of the production backend).

The other users can meanwhile work with their local frontends on the production backend.

When you are ready for release, make the necessary changes in the production backend (if there are changes in table structures). Make a copy of your dev frontend and link the tables from prod backend. This is the new prod frontend, which is distributed to all users.