Known issues with replication?

[Guest]

Are there any known issues with the replication of Access databases? Our
netadmin group has implemented dfsshares and is replicating our Access dbs.
They tell me they have pointed all the users to a single site for accessing
the db, and the replication is for backups.

 

[Douglas J. Steele]

Replication is only intended for data: tables only. If your application
isn't split into a front-end (containing the queries, forms, reports, macros
and modules), linked to a back-end (containing the tables and
relationships), it should be, and only the back-end should be replicated.

 

[aaron.kempf]

MDB replication is for babies. it's not reliable or scalable.

keep your data in SQL Server and use REAL replication.

 

[aaron.kempf]

and if you used an Access Data Project; you woudln't have to worry
about 'replicating queries'

keep them all in one place; keep your data in one place and your SQL
statements in one place.

with MDB; you're faced with a maintenance nightmare

-Aaron

 

[Guest]

We are split into BE and FE, and they may be replicating the FE as well as
the BE. However, we are using the Auto FE Updater, so the actual FE in use is
the copy on the user's workstation unless I'm making a change to the FE on
the server. That should replicate OK as soon as I'm out since it's only
locked while I'm in it. My understanding (meager as it is) is that databases
don't replicate until they are closed. Do I need to ask them not to
replicate the FE even under those conditions?

 

[aaron.kempf]

if you used a real database; you wouldn't have to run around keeping
track of 'who is in the database and who isnt'

in Access Data Projects

a) that information is EASY to get to.
b) it's not necessary to kick people out for maintenance.

compact and repair?

ROFL

 

[Douglas J. Steele]

They definitely should not replicate the front-end. As I said, replication
is only intended for data, not program components.

 

[Guest]

Should the .mdw file be replicated since it contains the user accounts and
groups, which do change some? We have a lot more turnover than many
organizations.

Thanks,
Donna Thornhill

 

[Douglas J. Steele]

To be honest, I don't know whether the mdw can be replicated. However, it's
so small that simply copying it should be reasonable.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Should the .mdw file be replicated since it contains the user accounts and
groups, which do change some? We have a lot more turnover than many
organizations.

Thanks,
Donna Thornhill

 

[Guest]

THey are using DFS for replication, and are replicating just about everything
now through the dfsshares.

To be honest, I don't know whether the mdw can be replicated. However, it's
so small that simply copying it should be reasonable.

 

[aaron.kempf]

you should use Access Data Projects which supports real replication and
real security.

MDB is for cripples and retards.

-Aaron

 

[Douglas J. Steele]

Sounds as though you may not be using "replication" in terms of how Access
thinks of "replication".