cannot make table object container replicable

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Emmett Power - 19 Sep 2003 12:39 GMT

Hi,

I have a problem with my Access database. The database was a master
database in a replication set with two replicas. I compacted and
repaired the database. After this the database ceased to be a master
database.

I attempted to create a replica from the database to make it revert to
a design master. None of the other replication options - Recover
design master and so on - are available. But at that point I came up
with the following error message: cannot make table object container
replicable.

The message referred to the first table on the database. I deleted
that table and its relationships to see if that made any difference.
All that happened was that the error message then referred to the next
table on the database. I deleted that table and the same thing
happened.

The database has about 28 tables with around 40 relationships. None of
the relationships have an enforced referential integrity.

Does anybody have any suggestions how to recover the master design or
to make the table replicable again?

Should I worry about the data in the database?

I'd appreciate any sugegstions.

Regards

Emmett Power

Reply to this Message

ProfW7 - 21 Sep 2003 03:54 GMT

My understanding is the "compacting/repair" is a "no-no" in a replicated set
because it keeps tract of the "space" and then when you compact it then it
causes errors. That is what I haver heard ... so I have never compact/repaired
my XP ACCESS database. I'm just learning and managing a Replication Manager
4.0 set of replicas.
Everyone has ACCESS XP and Replication Manager 4.0. Anyone with ACCESS97
cannot look at the database. We put a "Read Only" version on our LAN for
anyone to access. I have not seen anyproblem of when people access the
database. I would love to learn more from anyone. Roy, ProfW7@aol.com

Reply to this Message

Michael \(michka\) Kaplan [MS] - 21 Sep 2003 13:33 GMT

"ProfW7" <profw7@aol.com> wrote...

> My understanding is the "compacting/repair" is a "no-no" in a replicated set
> because it keeps tract of the "space" and then when you compact it then it
> causes errors.

This is COMPLETELY untrue.

> That is what I haver heard ...

I would love it if you could recall where you heard it, as this type of
misinformation is not helpful to customers.

> so I have never compact/repaired my XP ACCESS database.

Signature

MichKa [MS]

This posting is provided "AS IS" with
no warranties, and confers no rights.

Reply to this Message

Michael \(michka\) Kaplan [MS] - 21 Sep 2003 13:38 GMT

More detail please....

1) version of Access?
2) OS?
3) Compact/repair method?
4) Done locally or across a network?
5) Are you sure it is still replicated?

Also, note from your description:

> The database has about 28 tables with around 40 relationships. None of
> the relationships have an enforced referential integrity.

These are not real relationships, in that case. They are just pretty lines.
It is only enforced relationships that can be used by Jet to determine the
nature of the structure of the database for purposes like QPE optimization.
Probably not the cause of the problem, but the comment caught my eye.

Signature

MichKa [MS]

This posting is provided "AS IS" with
no warranties, and confers no rights.

> Hi,
>
[quoted text clipped - 28 lines]
>
> Emmett Power

Reply to this Message

Emmett Power - 22 Sep 2003 10:39 GMT

Hi Michael,

Answers to questions:

1) Access Version = 2000 (9.0.3821 SR-1)
2) OS = W2000 Professional
3) Compact/repair = Tools/Database Utilities/Compact & Repair Database
4) Compact and repair was done locally.
5) What do you mean by "Are you sure it is still replicated?" I am
trying to create a new replica.

Thanks for your help.

Regards

Emmett

> More detail please....
>
[quoted text clipped - 46 lines]
> >
> > Emmett Power

Reply to this Message

Michael \(michka\) Kaplan [MS] - 22 Sep 2003 15:17 GMT

"Emmett Power" <Emmett@Silico-Research.com> wrote...

> 1) Access Version = 2000 (9.0.3821 SR-1)
> 2) OS = W2000 Professional
> 3) Compact/repair = Tools/Database Utilities/Compact & Repair Database
> 4) Compact and repair was done locally.
> 5) What do you mean by "Are you sure it is still replicated?" I am
> trying to create a new replica.

The error would tend to indicate that it is no longer replicated, and that a
non-replicated database is being made into a replica.

A replicated database can be turned into a non-replicated database if it was
corrupt and had to be repaired. This would explain why the other options are
disabled, and I would suggest that this is probably what happened.

Signature

MichKa [MS]

This posting is provided "AS IS" with
no warranties, and confers no rights.

Reply to this Message

Emmett Power - 22 Sep 2003 20:11 GMT

Michael,

Is there any way to make it the master file and to make it replicable
so that I can share the date in the database with other users?

Thanks

Emmett

> "Emmett Power" <Emmett@Silico-Research.com> wrote...
>
[quoted text clipped - 11 lines]
> corrupt and had to be repaired. This would explain why the other options are
> disabled, and I would suggest that this is probably what happened.

Reply to this Message

Michael \(michka\) Kaplan [MS] - 23 Sep 2003 00:49 GMT

Not until the corruption problem is solved, no.

Signature

MichKa [MS]

This posting is provided "AS IS" with
no warranties, and confers no rights.

> Michael,
>
[quoted text clipped - 20 lines]
> > corrupt and had to be repaired. This would explain why the other options are
> > disabled, and I would suggest that this is probably what happened.

Reply to this Message

Emmett Power - 23 Sep 2003 20:15 GMT

OK.

Is there a way of determining what the corruption in the database is
given that the database is opeing fine and appears to have no other
visible problems other than this problem with replication?

Thanks

Emmett

> Not until the corruption problem is solved, no.
>
[quoted text clipped - 27 lines]
> are
> > > disabled, and I would suggest that this is probably what happened.

Reply to this Message

Michael \(michka\) Kaplan [MS] - 23 Sep 2003 22:25 GMT

The error sometimes points to the object with the problem? Otherwise you can
try importing all objects to a new database.

Signature

MichKa [MS]

This posting is provided "AS IS" with
no warranties, and confers no rights.

> OK.
>
[quoted text clipped - 37 lines]
> > are
> > > > disabled, and I would suggest that this is probably what happened.

Reply to this Message

Emmett Power - 24 Sep 2003 13:07 GMT

MichKa,

I have imported the tables and the functions into a new database which
I created on the same drive as the original.

I am getting a number of error messages that may help with
diagnostics:

1) When importing some of the tables I get the following message
"Unknown function in table level validation expression". As well as
importing the original table, say Contacts, a copy of the table
Contacts1 is created. This occurs on five tables, some of which are
very simple.

2) Contacts is not replicable but preserves the lookup functions.
Contacts1 is replciable but does not preserve the lookups.

3) When opening Contacts I get the following error message: "The
expression that you entered has a function name that Microsoct Access
cannot find".

4) When I attempt to open the functions/modules I get the following
error message: "Error accessing file. Network connection may have been
lost".

5) When opening a form with subforms I get the following error
message: "The LinkMasterFields property setting has produced this
error: 'Error accessing file. Network connection may have been lost'."
Other form both with and without subforms open fine.

Does this offer any clues as to what has gone wrong?

Thanks

Emmett

> The error sometimes points to the object with the problem? Otherwise you can
> try importing all objects to a new database.
[quoted text clipped - 46 lines]
> are
> > > > > disabled, and I would suggest that this is probably what happened.

Reply to this Message

Michael \(michka\) Kaplan [MS] - 25 Sep 2003 13:33 GMT

"Emmett Power" <Emmett@Silico-Research.com> wrote...

> I have imported the tables and the functions into a new database which
> I created on the same drive as the original.
>
> I am getting a number of error messages that may help with
> diagnostics:

It may just be different terminologies between us, but I am probably much
more confused now....

> 1) When importing some of the tables I get the following message
> "Unknown function in table level validation expression". As well as
> importing the original table, say Contacts, a copy of the table
> Contacts1 is created. This occurs on five tables, some of which are
> very simple.

Is the data okay? You can always recreate tables.

> 2) Contacts is not replicable but preserves the lookup functions.
> Contacts1 is replciable but does not preserve the lookups.

???? -- The new db is not a replica so how can anything be replicable?

> 3) When opening Contacts I get the following error message: "The
> expression that you entered has a function name that Microsoct Access
> cannot find".

This would be the missing validation rule?

> 4) When I attempt to open the functions/modules I get the following
> error message: "Error accessing file. Network connection may have been
> lost".

Did you try importing objects one at a time, or all at once? And if you just
import one object, how does that one object do?

> 5) When opening a form with subforms I get the following error
> message: "The LinkMasterFields property setting has produced this
> error: 'Error accessing file. Network connection may have been lost'."
> Other form both with and without subforms open fine.

There really seems to be some pretty deep corruption here.

> Does this offer any clues as to what has gone wrong?

Well, I do not know of any professional developer who implements replication
on anything but the backend database, containing the tables. Replicating the
frontend objects (i.e. forms, reports, modules) is a receipe for bloat,
instability, and corruption -- the latter two of which appear to be biting
you fiercely.

Signature

MichKa [MS]

This posting is provided "AS IS" with
no warranties, and confers no rights.

Reply to this Message