We presently have a DB residing on our LAN server and are
considering splitting it to permit modifications to the
front-end without booting everyone out of program.  I'm
not sure that I totally understand the concept of
splitting the DB and have a few questions:

1.  The present thought is to split the DB leaving the
front-end in the directory on the server where it
presently resides and to place the backend (tables) in
another directory on the same server.  I know this will
not reduce network traffic.  However; it will a least
keep the front-end on the server and any modifications
done will be available realtime to several users. Is this
a practical option or does one have to place a front-end
on 35 PC's and find a method of updating them all with
the latest changes made to the front-end from time to
time?

2.  We have full security on the existing DB and wonder
if there are any negative consequences of splitting the
DB at this time?

TIA