the synchronization failed because a design change could not be applied

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Nick Kilpasis - 15 Apr 2005 20:25 GMT

Hello All
After two week changing and adding tables on my database
I have the synchronization failed message on my screen
Can anybody tell me how I can find what new relation or field change is
causing thise problem ?
Is there a system table or any other tools that can report this.

Please Help
Many Thanks
Nick

Reply to this Message

Michael \(michka\) Kaplan [MS] - 15 Apr 2005 20:46 GMT

MSysSchemaProb should have the info, It is a hidden, system table.

Signature

MichKa [Microsoft]
NLS Collation/Locale/Keyboard Technical Lead
Globalization Infrastructure, Fonts, and Tools
Blog: http://blogs.msdn.com/michkap

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

> Hello All
> After two week changing and adding tables on my database
[quoted text clipped - 6 lines]
> Many Thanks
> Nick

Reply to this Message

Nick Kilpasis - 15 Apr 2005 21:57 GMT

That’s great thank you
I have two records with the same problem for two deferent tables
1. “The database engine could not lock table 'ProjectItems' because it is
already in use by another person or process.”
2. The database engine could not lock table 'Items' because it is already
in use by another person or process.
No one is using the master or replica but my PC with one MSAccess running.
Do you have any suggestions?

Thank’s again

Reply to this Message

Michael \(michka\) Kaplan [MS] - 18 Apr 2005 06:18 GMT

Have you replicated just the backend, or have you also replicated the front
end with Access objects in it, as well?

Signature

> That?s great thank you
> I have two records with the same problem for two deferent tables
[quoted text clipped - 6 lines]
>
> Thank?s again

Reply to this Message

David W. Fenton - 23 Apr 2005 21:27 GMT

> I have two records with the same problem for two deferent tables
> 1. ?The database engine could not lock table 'ProjectItems'
[quoted text clipped - 3 lines]
> No one is using the master or replica but my PC with one MSAccess
> running. Do you have any suggestions?

Two things in addition to Michael's suggestion that you're
replicating the front end (which is never going to be successful in
the long run):

1. have you deleted the LDB file associated with the design master?
It could be that the LDB has corrupt data in it that is not being
removed somehow. If the LDB file is not getting deleted when you
exit Access, this would cause the error to continue to exist.

2. have you compacted the design master? Sometimes this error comes
up when a db is flagged corrupt.

Signature

David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

Reply to this Message