Hello All
I have a split FE/BE A97 mdb. The BE (278mb) is on a server, with 7 FEs
(115mb) on 7 PCs: the PCs are running W2K professional, with 512mbRAM on
each. This is all starting to creak a bit: we are increasingly frequently
getting database corruptions and "can't open any more tables ..." and
other
messages that I think are due to our being close to access's limits in
terms
of sharing and effective mdb size.
The general recommendation seem to be move to SQLserver, but the cost of
this looks prohibitive, so I am wondering about splitting the application
in
7 separate, complete mdbs (i.e. FE and BE together in one mdb), one for
each
PC. This would reduce the amount of data in each mdb to a seventh of what
is
currently being accessed by each user, and it would also do away with the
need for any sharing - which presumably would make for a more
stable/robust
environment.
The problem would be implementing the regular changes that I have to make
to
the design of various tables, forms, re****ts etc., but for this I wondered
if I could make the 7 mdb replicas, to be synchronised daily. I would not
want to synchronise the data (as this would obviously result in all the
data
coming together), but I would want to synchronise the tables' designs and
all the forms/ re****ts/queries etc.
Does this sound feasible? Given that the working practices in the office
could be altered so that the users would not need access to each other's
data, I think perhaps this solution might just work ... or have I
overlooked
something??!!
I would be very grateful for any advice.
Thanks
Leslie Isaacs
|
