Microsoft KB Archive/236539

= MOD2000: Errors When You Open Codelib.mdb from Read-Only Share =

Article ID: 236539

Article Last Modified on 9/3/2002

-

APPLIES TO


 * Microsoft Office 2000 Developer Edition

-



This article was previously published under Q236539



Moderate: Requires basic macro, coding, and interoperability skills.



SYMPTOMS
When you try to open the Codelib.mdb file in Code Librarian from a read-only share, you may receive the following error message:

Invalid database format.

When you click OK, you receive the following error message:

Code Librarian Assert:

Module:modMain

Sub:AddSubNodes

Err:3709

Error:Operation is not allowed on an object referencing a closed or invalid connection.

As you continue to click OK, you continue to receive the following two errors messages:

Code Librarian Assert:

Module:modMain

Sub:AddSubNodes

Err:3704

Error:Operation is not allowed when the object is closed.

-and-

Code Librarian Assert:

Module:modMain

Sub:AddSubNodes

Err:3265

Error:Item cannot be found in the collection corresponding to the requested name or ordinal.

This behavior continues, and you cannot stop the error messages or do anything else from within Code Librarian.



RESOLUTION
To resolve this problem, obtain Microsoft Office 2000 Developer Service Release 1 (SR-1).

To obtain SR-1, click the article number below to view the article in the Microsoft Knowledge Base:

253566 MOD2000: How to Obtain and Install Microsoft Office 2000 Developer Service Release 1 (SR-1)

To temporarily work around this problem, move the Codelib.mdb file to your local computer or to a share that is not read-only.

If you receive the error messages described in the "Symptoms" section, you must force Code Librarian to quit. To do so, follow these steps:
 * 1) In Microsoft Windows 95 or Microsoft Windows 98, press CTRL+ALT+DEL to open the Close Program dialog box.

In Microsoft Windows NT or Windows 2000, press CTRL+ALT+DEL, and then click Task Manager.
 * 1) Click Code Librarian, and then click End Task.

NOTE: In Windows NT or Windows 2000, you must click the Applications tab to do this.
 * 1) If you have any projects open, save your changes, and then close the Visual Basic Editor. Also, quit the application in which you were using the Visual Basic Editor. If you do not close and re-open your projects, you are unable to re-open Code Librarian.
 * 2) Re-open your projects, and re-open Code Librarian.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Microsoft Office 2000 Developer SR-1.



Steps to Reproduce the Behavior
 Set up a folder on a computer on your network to be shared on the network. Set permissions for everyone to have read-only access. Insert the Office Developer 2000 CD and copy the following file from the CD to the folder that you set up:

\ODETools\V9\Codelib.mdb

 On another computer on the network that has Microsoft Office 2000 Developer installed, open any Office 2000 program that uses the Visual Basic Editor, and then press ALT+F11. On the Add-ins menu, if you see Code Librarian, skip to step 6. On the Add-Ins menu, click Add-In Manager. Click Code Librarian, and then under Load Behavior, click to select the Loaded/Unloaded check box. Click OK.</li> On the Add-ins menu, click Code Librarian.</li> In the Code Librarian, click Open on the File menu.</li> If your local Codelib.mdb file is not already open, browse to it, and open it first. By default, the Codelib.mdb file is in the following location:

Program Files\Microsoft Office\ODETools\V9\Codelib.mdb

</li> Leave the local Codelib.mdb file open.</li> On the File menu, click Open.</li> Locate the read-only share where you placed the other copy of the Codelib.mdb file, and then open it.

Note that you receive the error messages mentioned in the "Symptoms" section.</li></ol>

Additional query words: pra Err 3709 module: modmain sub: addsubnodes error: item

Keywords: kbbug kbpending KB236539

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.