Database Splitter: Update?

[Guest]

Hello everyone,

I've been reading the forums about splitting a database, but I'm still
not 100% clear on it. I'm creating a database system for my boss (who has no
experience with Access) and several other users at different branch
locations. I realize splitting the database into a front-end and a back-end
will be the most efficient way for the users to enter data and generate
reports.

Let me see if I am getting this right: once I split the datbase, I'll
have a front-end, which I will put on each user's computer, and a back-end
which I'll place on a shared network drive which each user has access rights
to.

I will be the one updating and maintaing the tables bi-weekly by
importing data from an excel spreadsheet. My question is: Can I update my
copy of the front-end (example: A form layout, colors, font), and have those
changes reflected on the other user's desktops?

Sorry this is so long and thanks in advance!

 

[Ken Snell [MVP]]

You can update your front end copy, and then you would provide a copy of
that modified front end to each of your users; they would replace their copy
with your new copy.

Your changes will not be seen in their front ends unless you give them a
copy of the front end.

 

[Guest]

Thanks for your help. You have answered my question. However, I have
another: When I want to do an import from an excel spreadsheet to update the
tables, would it be best to do this on the back-end by deleting the records
and replacing them or from the front-end? Thanks again.

 

[Ken Snell [MVP]]

I prefer interacting with the backend via a front end for all data updates.
That allows you to make data changes while others are still using the
backend.
--

Ken Snell
<MS ACCESS MVP>