replicated database and saving reports

[Guest]

I have a report that when I access it in a replicated database I can't save
the report once I view it. The save as button is disabled. I am able to do
it in the master copy. Is there a way to make the save as button enabled in
the replicated databases?

Any help would be greatly appreciated.

Lisa

 

[David W. Fenton]

I have a report that when I access it in a replicated database I
can't save the report once I view it. The save as button is
disabled. I am able to do it in the master copy. Is there a way
to make the save as button enabled in the replicated databases?

Only in the design master.

But you're doing it wrong -- you should have a split database, with
the data tables in one MDB (the "back end") and everything else in
another (the "front end"). Only the back end data tables should be
replicated, because replication is a Jet technology and doesn't work
reliably over the long with anything but pure Jet objects (tables
and queries).

And the DM and your replica are both replicated -- they are two
members of the replica set, but one of them is a special replica,
the only one that allows design changes.

 

[Guest]

David,

Thanks for your response. It was a great help. I normally work in a split
databases, but wasn't sure how to work this with a replication when they are
on different servers. How do you connect the forms / query database to the
table database (be.mdb) when they are on different servers. Can I copy the
forms/query database to each server and import links to the tables in the
table database (be.mdb)

Any help you can provide would be great.

Thanks.

Lisa

 

[David W. Fenton]

I normally work in a split
databases, but wasn't sure how to work this with a replication
when they are on different servers. How do you connect the forms
/ query database to the table database (be.mdb) when they are on
different servers. Can I copy the forms/query database to each
server and import links to the tables in the table database
(be.mdb)

The linked table manager can be used to change the links, or you can
provide a UI for the user to pick the location of the back end on
the server. There have been dozens of solutions for relinking tables
posted here and elsewhere over the years.

 

[Peter Hibbs]

Lisa

To re-link the front end to the back end automatically whenever you
update the front end file have a look at :-

http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE_ReLink.mdb'

which shows how to do this.

HTH

Peter Hibbs.