Hello All

I have a split A2k db on a 30-user network, with each workstation having its
own frontend (on its C drive) and all with linked tables which are in a db
on the fileserver.
All works fine, except that it is very laborious when I make design changes
to the frontend - I have to manually copy and past the new frontend onto
everyone's workstation. I think this could be done with a proper system of
version control and batch copying, but I don't have the expertise to do
this - and I'm the nearest thing we have here to an expert!! I was
wondering, though, about having a single fronend, on the server, that
everyone uses. Although there are about 30 users in total, it would be very
rare that more than 4-5 of them wanted access to the db at the same time.

Is this idea worth pursuing, or is it a definite no-no?

I would be very grateful for any advice.

Many thanks
Leslie Isaacs