Splitting Database

[Doug_C]

Hello!!

I have a quick question. I never split a database before but this one I just
created will be user by multiple users at once. So my question is this:

After I split the database Frontend - Backend, I may need to do maintenace.
I believe if it is a Form or Report, I would go into the Frontend and if it a
table the backend correct? Or, do I do ALL maintenance from the Frontend and
the Backend is just to store the data?

Don't mean to sound dense about this but, I have a lot of fate in folks that
answer to this forum and trust your guidance which has helped gain a better
understanding of Access.

Thank you!!!

 

[Marshall Barton]

I have a quick question. I never split a database before but this one I just
created will be user by multiple users at once. So my question is this:

After I split the database Frontend - Backend, I may need to do maintenace.
I believe if it is a Form or Report, I would go into the Frontend and if it a
table the backend correct? Or, do I do ALL maintenance from the Frontend and
the Backend is just to store the data?

Don't mean to sound dense about this but, I have a lot of fate in folks that
answer to this forum and trust your guidance which has helped gain a better
understanding of Access.

This is not an unusual question the first time around so you
are not being "dense". The answer is that you must do the
maintenance in the database that contains the object you are
modifying. I.e. you had the right idea all along.

The UI will not let you modify a table's design from the
front end, so you were safe from that in any case. The
thing that trips most folks is managing the Relationships
between the tables. The UI allows you to modify the front
end's view of the relationships, but that has no effect on
the real relationships in the back end. Just be extra
concientious about going to the back end to work in the
Relationships Window.