Microsoft Knowledge Base Email Alertz

KBAlertz.com: (172162) - When you try to open a replica, you may receive the following error message Name conflicts with existing module, project or object library. and you are unable to open the replica.

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com

ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 172162 - Last Review: January 20, 2007 - Revision: 3.4

ACC97: "Name Conflicts..." Error When Opening Replica

This article was previously published under Q172162
Advanced: Requires expert coding, interoperability, and multiuser skills.

On This Page

SYMPTOMS

When you try to open a replica, you may receive the following error message
Name conflicts with existing module, project or object library.
and you are unable to open the replica.

CAUSE

A conflict is preventing Microsoft Access from compiling and saving the replica's Visual Basic for Applications project.

The first time you open a replica following synchronization, Microsoft Access automatically compiles and saves the replica's Visual Basic for Applications project. In the Design Master, you cleared the Replicable property on a module's property sheet, and then synchronized with the replica. However, an error prevented Microsoft Access from updating the replica's project. So, although the module no longer appeared in the replica, it had not been removed from the project. You then opened the Design Master, made the module replicable again, and synchronized with the replica. You receive the error because Microsoft Access is attempting to update the project again; however, it is now attempting to add a module to the project that is already there.

RESOLUTION

Open the Design Master and make the modules unreplicable. After synchronization, you can open the replica. If you want the modules to be transferred to the replica during synchronization, rename them.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access 97. This problem no longer occurs in Microsoft Access 97 Service Release 1.

NOTE: Stand-alone Microsoft Access 97 Service Release 1 is not currently available, but you can update your copy of Microsoft Access 97 to Service Release 1 by downloading Microsoft Office Service Release 1 from Microsoft's Web site at:
http://office.microsoft.com/en-us/assistance/HA010449921033.aspx (http://office.microsoft.com/en-us/assistance/HA010449921033.aspx)

MORE INFORMATION

Steps to Reproduce Problem


  1. Start Microsoft Access and open a new blank database.
  2. Open a new blank module and type the following procedure:
           Function test1()
              Msgbox "test"
           End Function
    						

    Close the module and save it as Module1.
  3. Open a new blank module and type the following procedure:
           Function test2()
              Msgbox "test"
           End Function
    						

    Close the module and save it as Module2.
  4. On the Tools menu, point to Replication, and click Create Replica. When prompted to close the database, click Yes. When prompted to make a backup, click No.
  5. In the Location Of New Replica dialog box, note the location and file name of the new replica. Click OK.
  6. Click OK when prompted to reopen the database, which is now the Design Master.
  7. Close the Design Master and open the replica. Note that Module1 and Module2 appear when you click the Modules tab. Close the replica.
  8. Open the Design Master.
  9. Right-click Module1 and click Properties; clear the Replicable check box.
  10. Right-click Module2 and click Properties; clear the Replicable check box.
  11. Synchronize with the replica, and then close the Design Master.
  12. Open the replica. When you receive the "Automation error" message, click OK. Note that when you click the Modules tab, the two modules do not appear on the list.
  13. Close the replica.
  14. Open the Design Master.
  15. Right-click Module1 and click Properties. Click to select the Replicable check box, and then click OK.
  16. Synchronize with the replica, and then close the Design Master.
  17. Open the replica. Click OK when you receive the "Automation error" message.
  18. Click Yes when you receive the message:
           'Module1' has been changed since the last time you opened it, either
           by another user or because another instance of it was opened on your
           own machine. Do you want to replace the changes that you or another
           user made?
    						
  19. Notice that Module1 appears when you click the Modules tab. Close the replica.
  20. Open the Design Master.
  21. Right-click Module1 and click Properties. Click to select the Replicable check box, and then click OK.
  22. Synchronize with the replica, and close the Design Master.
  23. Open the replica. Note that you receive the error

    Name conflicts with existing module, project or object library.

REFERENCES

For more information about problems with projects in replicas, please see the following article in the Microsoft Knowledge Base:

171207  (http://kbalertz.com/Feedback.aspx?kbNumber=171207/EN-US/ ) Removing Replicated Module Causes Automation Error

APPLIES TO
  • Microsoft Access 97 Standard Edition
Keywords: 
kbdownload kbbug kberrmsg KB172162
Retired KB ArticleRetired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please