Replication - Error "Cannot Create a new replica because....could

[Guest]

I am attempting to create a replica after creating the design master and get
this message:
"Cannot make a new replica because qryAppend Employees to History object in
Tables container could not be made replicable"

I've looked at that query and it's properties show it as replicable. I
opened the query in design view to see if there's anything odd going on,
which there isn't. Has anyone ever seen this before? This is a
make-or-break issue for me, as I MUST be able to replicate my database.
HELP~!!!!!!!

 

[Joan Wild]

I am attempting to create a replica after creating the design master
and get this message:
"Cannot make a new replica because qryAppend Employees to History
object in Tables container could not be made replicable"

I've looked at that query and it's properties show it as replicable.
I opened the query in design view to see if there's anything odd
going on, which there isn't. Has anyone ever seen this before? This
is a make-or-break issue for me, as I MUST be able to replicate my
database. HELP~!!!!!!!

I suppose the good news is that you shouldn't replicate queries (or
forms/reports/macros/modules). Replication is meant for data only i.e.
tables.

Split your database and replicate just the backend. Each user will have a
copy of the frontend linked to some replica. If/when you have changes to
the frontend, you just distribute it to the users.

 

[Guest]

Just want to make sure I am clear on this.

Open my database and use the Database Splitter to create the front end and
back end files.

Open the back end and create the replicas.

Make copies of the front end and distribute - then update the front end to
link to the replica instead of the original back end?

I am in Oregon and this database is going to be headquartered in Atlanta and
then distributed to field offices all over the country. I will not have
direct access to the files - I have to email everything to people who are not
savvy about Access. I want everything to be as uncomplicated as possible. I
was hoping to be able to have the field people put the replica in their
briefcase and then synchronize whenever they are connected to their network.
Is there a better way?

Thanks a bunch for any advice you can give!!

 

[Joan Wild]

Just want to make sure I am clear on this.

Open my database and use the Database Splitter to create the front
end and back end files.

Since you already applied replication (you said you had a design master),
you'll need to start over with an unreplicated database. Split it and then
replicate just the backend.

Open the back end and create the replicas.

Make copies of the front end and distribute - then update the front
end to link to the replica instead of the original back end?

Each user will link to whatever replica they are using (I assume you'll have
a number of them).

I am in Oregon and this database is going to be headquartered in
Atlanta and then distributed to field offices all over the country.
I will not have direct access to the files - I have to email
everything to people who are not savvy about Access.

You cannot email replicas around. They must be setup on site. You may be
missing some key points about setting up replication. I suggest you read up
on it.

For Jet 4.0
http://support.microsoft.com/?id=190766 - white paper
http://support.microsoft.com/?id=282977 - FAQ

Also see
www.trigeminal.com - excellent replication site
http://support.microsoft.com/support/access/content/repl/replication.asp

These should give you enough information to set up replication. If you have
further questions, I'd suggest you ask in the
microsoft.public.access.replication group.

I want
everything to be as uncomplicated as possible. I was hoping to be
able to have the field people put the replica in their briefcase and
then synchronize whenever they are connected to their network. Is
there a better way?

Replication is complicated; you really can't take shortcuts. Using the
briefcase is definitely not the way to go. You might also consider using
Terminal Server rather than replication. See
http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html for some additional
thoughts.

 

[Guest]

I assumed I would start with the unreplicated DB.

I was also hoping to allow remote staff to use the Briefcase replication
technique, as it is so easy to do (the easier the better for these folks).
Can that still happen by having them drag the back-end file into their
briefcase and the replica will automatically be created - and then just COPY
the front-end file into the Briefcase - or is there something else that has
to be done?

This is my first experience with replication so any information that will
make this successful is most welcome - I have read the articles you suggested
- but there's nothing in there about splitting the database first. I have
looked for recommendations on that in the past and wasn't able to find
anything definitive - so if you can provide me with the steps required, I
would really appreciate it.

 

[Joan Wild]

I was also hoping to allow remote staff to use the Briefcase
replication technique, as it is so easy to do (the easier the better
for these folks).

Everything I've read regarding Briefcase replication was "don't use it".

This is my first experience with replication so any information that
will make this successful is most welcome - I have read the articles
you suggested - but there's nothing in there about splitting the
database first.

I don't have it handy, but I recall that one of the items in the FAQ says
not to replicate frontend objects.

I strongly urge you to post your questions in the replication newsgroup, as
that is where you'll find the experts on it.

Developer - Office Solutions ...Access...Replication