Database Synchronization error

[ChrisK]

I am using Access 2007 with version 2003 data files with a small replica set.
When I try to synchronize the replicas with the design master, I am getting
a error that a design change is preventing the sync from completing. After a
bit of Googling, I found that the hidden table MSysSchemaProb has the
specific error. Here's what I found:

Command: Delete column
Error: 3211
Error Text: The database engine could not lock table
'tblPriceCalculationData' because it is already in use by another person or
process.

Is there a solution on this one?

thanks in advance...

 

[David W. Fenton]

I am using Access 2007 with version 2003 data files with a small
replica set.
When I try to synchronize the replicas with the design master, I
am getting
a error that a design change is preventing the sync from
completing. After a bit of Googling, I found that the hidden
table MSysSchemaProb has the specific error. Here's what I found:

Command: Delete column
Error: 3211
Error Text: The database engine could not lock table
'tblPriceCalculationData' because it is already in use by another
person or process.

Is there a solution on this one?

That's usually a corruption error. Can you identify the replica that
is producing the error? If you can, compacting it might fix the
problem.

If not, you might try rolling back the design change in the DM and
then attempting to synch again. If you can then synch the data
changes you might be able to completely discard the problematic
replica and then implement the design change with a replacement
replica.

But there are a lot of "ifs" in that advice...

 

[aaron.kempf]

Yah, if you've got corruption, it basically means

NEENER-NEENER, you're a fucking idiot for using Jet

Move to SQL Server

Anyone using Jet for any reason (and subjecting your customers to
corruption) should be FIRED and then SPIT UPON.

-Aaron