Mdb/Mde/Replica advice needed

[Brambojr]

At work we are having a few difficulties. Let me explain.

Some computers are on Win 98, others on Win 2000 with one or two on XP - they don't files share well. The mdb's get locked up. Then we have to compact a repair, but everyone has to get out first, and we working in two buildings - this never works and is NEVER easy.

Problem two: We are beginning to use Tablet PC's that connect wirelessly to the network. I don't like the huge lag whenever I want to open an mdb. I'd like to save it to the c: drive.

So . . . I am thinking about making replicas to sit on each computer. Or should I use an mde or mdb? Or would some fusion of the two work best?

These databases (definitely plural) are often modified, so the db will need to auto-update. Will a replica simplify this? I know it can be done in code.

What is the safest, most stable method of distributing these db's over a hodge podge network? Brambojr

 

[Brambojr]

On further review, here is my evolving plan:

Steps:

Create a master db with tables (prevent unnecessary proliferation). Split Master db. Give back end a db password and re-link tables.

Create the ensuing db's (forms and reports customized to departments). Create (unsure of # needed) replica(s) of each baby db - each baby db has only tables LINKED to the master db.

Put replicas on each PC in area and change shortcuts to reflect changes.

General:

I do not want to make these mde's since the forms and reports are changed often enough.

Each replica will have code that will check to see if changes have occured as it opens. It will update automatically - I know the code is out there.

Questions:

So, how many replicas do I really need? I want to put it right onto each hard drive - is this realistic?

Is this a viable solution? And more importantly will it withstand the problems created by Win98, Win2000, WinXP's failure to share files well? Does anyone have any experience in this? Brambojr