DAO.Database error 3492 when attempting to sync replica to design master

Posted on 2008-10-03
Last Modified: 2012-05-05
We currently use DAO 3.6 with Access 2003.

To update cleint databases, we create templates from the design master and distribute those templates.

For some clients, we get this error:

3492 - The synchronization failed because a design change could not be applied to one of the replicas.

the line that causes this error is: db.Synchronize sTemplate, dbRepImportChanges

I check the MSysSchemaProb table and found this information
Column = Value
Command = Set
Error = 3011
ErrorText = The Microsoft Jet database engine could not find the object 'qryCityByCityStateCode'.  Make sure the object exists and that you spell its name and the path name correctly.
SchemaVersion = 10833
Text1 = Tables
Text2 = qryCBCSC

I checked the upgrade template and the query is there, i have tried rebuild the database into a blank version of the same db with no luck, i ran code to see if there are any conflicts listed and there are not. please help. Thank you.
Question by:DevLSS
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
LVL 38

Expert Comment

ID: 22636320
Often Access error messages are cryptic.  Even though the query exists, there may have been a design change within the query itself that is causing the error with the upgrade template.   Try comparing the query in design view or in sql view between the upgrade template  and Design master.  

Hope this helps.

Author Comment

ID: 22636970
i did compare them and they are identical, the same exact SQL and design view
LVL 38

Expert Comment

ID: 22637384
hmmm....just thinking....I know you said the query was exactly the same in sql and in design view....but would you have noticed if the order of the columns in the query grid or query sql was slightly different?  It seems to me that if the select statement was changed from >>>>>Select A, B, C  to >>> Select A,C, B  this might a subtle change between the design master and the upgrade template that you might have overlooked.  And it could also explain why the error goes away when you rebuild the db..
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 22637690
i could see that as a problem, but why would it work for one DB and not another?
LVL 38

Expert Comment

ID: 22639358
I  assume that the replicas were created at different times, and all but one created after the design change to the query was made in the master...... the one replica that was created before the design change is the one that caused the conflict........which went away when you created a new replica.  Is that possible??

Author Comment

ID: 22643092
Yes, the replicas were created at different times, but i don't see how that would be the problem because aren't all the replicas tied to the deisgn change history of the design master?
LVL 38

Expert Comment

ID: 22643222
Yes, that is what the synchronization process is all about. .....if a design change is made to the master, it won't present itself as a conflict until the next attempt to which time the conflict will be resolved and disappear (as in your case). Timing does matter.

Your last question was related to how it was possible that only the one replica was showing  a conflict....and the answer is that the one replica was created from the master as it existed before the design change to the query was made.  The other replicas did not have the conflict because they were probably created after the design change was made, and therefore, those replicas had already included the  design change before the synchronization that is the subject of this post was performed.

Accepted Solution

DevLSS earned 0 total points
ID: 22644173
none of these replicas could have had the query, because it was added to the design master this time. so when the template is applied to the replicas, the query is being created.

I also checked the upgrade template against the design master and the query is identical in every way.

I can try rebuilding the database into a newer version of the database(which i prefer to find a solution and not use this workaround). That will usually do the trick.
LVL 38

Expert Comment

ID: 22644219
Ok,then I have no other ideas as to why only one of your replicas had the conflict.  If it doesn't happen very often, your workaround should suffice.

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

You can of course define an array to hold data that is of a particular type like an array of Strings to hold customer names or an array of Doubles to hold customer sales, but what do you do if you want to coordinate that data? This article describes…
Did you know that more than 4 billion data records have been recorded as lost or stolen since 2013? It was a staggering number brought to our attention during last week’s ManageEngine webinar, where attendees received a comprehensive look at the ma…
In Microsoft Access, learn different ways of passing a string value within a string argument. Also learn what a “Type Mis-match” error is about.
In Microsoft Access, when working with VBA, learn some techniques for writing readable and easily maintained code.

710 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question