multiple be

[hai]

using Access 97 in multi-user environment. I have a split
Fe/Be database. Some of the data in the Be is common to
data in other Be's (different databases). Will I take a
hit on performance if I split out the common data into a
3rd Be and have the Fe link to multiple Be's? Outside of
not being able to enforce referential integrity, are there
any other issues I need to be concerned about (such as
corruption)? I expect about 50 simultaneous users for the
Be with the common data. If I don't merge the common data
into a seperate Be, there will be about 25 simultaneous
users.

Thanks!
-hai

 

[TC]

You need to have the FE open each BE & keep it open for the duration of the
FE run. This avoids the slow-down that can happen when the FE repeatedly
opens & closes the BE, with the associated creation & destruction of LDB
files on the BE pc. This is important for single-BE systems. It would
doubtless be ven more imprtant for multiple-BE ones. Use
dbengine.opendatabase to get this happening.

HTH,
TC

 

[hai]

I'm already familiar with using a persistant recordset to keep the ldb
from constantly being re-created. Do you think I'll take a hit on
speed and stability (since more users will be in it simultaneously)?

-hai

 

[TC]

I guess if you double the # of users, there may be a greater liklihood of
record-locking conflicts. It's hard to predict, you'd maybe just have to try
it & see.

As for corruption, I don't believe that having multiple BEs would increase
the chance of that - but I've never done it that way, so I can't speak from
experience. Maybe someone else can comment?

Cheers,
TC