To Split or not?

[HServ]

I've just finished a database for a small division of a company. There are
about 25 people who will be using it, but not on a regular basis, so high
traffic is not an issue. Since we are on a network, it makes sense to split
the database but there are a few issues:
- I will not be working here to maintain the database
- I probably won't be able to gain access to the user's computers to install
the front end
- The users don't know enough about Access to do things like link tables

I was thinking of loading the front-end onto a cd and then making it
available for users to put it onto their computers themselves.

How much maintainance is required if the back end is on the network? And can
I put a copy of the front end on the network as well as a safeguard? Would I
be better to not split the database and put the whole thing on the network?

Thanks

 

[Joseph Meehan]

I've just finished a database for a small division of a company.
There are about 25 people who will be using it, but not on a regular
basis, so high traffic is not an issue. Since we are on a network, it
makes sense to split the database but there are a few issues:
- I will not be working here to maintain the database
- I probably won't be able to gain access to the user's computers to
install the front end
- The users don't know enough about Access to do things like link
tables
I was thinking of loading the front-end onto a cd and then making it
available for users to put it onto their computers themselves.

How much maintainance is required if the back end is on the network?
And can I put a copy of the front end on the network as well as a
safeguard? Would I be better to not split the database and put the
whole thing on the network?
Thanks

No matter what, someone is going to need changes, so someone will need
to make those changes. Hopefully that someone can also handle any odd
events that would require changes to the front ends.

I vote to split it.

 

[Douglas J. Steele]

No question in my mind: split it.