Microsoft KB Archive/236535

= MOD2000: Opening Nonlibrary File in Code Librarian Causes Errors =

Article ID: 236535

Article Last Modified on 9/3/2002

-

APPLIES TO


 * Microsoft Office 2000 Developer Edition

-



This article was previously published under Q236535



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



SYMPTOMS
In the Code Librarian, if you already have a code library file open and you then try to open a file that is not a code library file, you first 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:The application requested an operation on an object with a reference to a closed or invalid Connection object.

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:The operation requested by the application is not allowed if the object is closed.

-and-

Code Librarian Assert:

Module:modMain

Sub:AddSubNodes

Err:3265

Error:ADO could not find the object in the collection corresponding to the name or ordinal reference requested by the application.

This continues and you cannot stop the error messages nor do anything else from within the 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, if you receive the error messages described in the "Symptoms" section, you must force the Code Librarian to quit. To do so, follow these steps:
 * 1) In Windows 95 or Windows 98, press CTRL+ALT+DEL to open the Close Program dialog box.

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

NOTE: In Windows NT, you must click the Applications tab to do this.
 * 1) If you have any projects open, save your changes and close the Visual Basic Editor. Also, quit the application in which you were using the Visual Basic Editor.
 * 2) Reopen your project(s) and reopen the Code Librarian.



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



MORE INFORMATION
If you do not have a code library file already open in the Code Librarian and you try to open a nonlibrary file, you receive only the first error:

Invalid database format.

Steps to Reproduce Behavior
 Open any Office 2000 program that uses the Visual Basic Editor and press ALT+F11. On the Add-Ins menu, if you see Code Librarian, skip to step 5. 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. On the Add-Ins menu, click Code Librarian.</li> In the Code Librarian, click Open on the File menu.</li> Open the Codelib.mdb file and leave it open.</li> On the File menu, click Open.</li> Locate the folder where the sample database Northwind.mdb is located. The default location for the sample database Northwind.mdb is:

C:\Program Files\Microsoft Office\Office\Samples\Northwind.mdb

</li> Try to open Northwind.mdb with the Code Librarian.

Note that you receive the succession of errors mentioned in the "Symptoms" section.</li></ol>

Additional query words: pra code librarian assert module: modMain sub: addsubnodes err: 3709

Keywords: kberrmsg kbbug kbcodelibrarian kbpending KB236535

-

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

© Microsoft Corporation. All rights reserved.