BUG: Opening an Access Repository in VCM Fails on Windows 95 and Windows 98 Computers When the .MDB Is Located on a Non-Local Network Share (267284)


The information in this article applies to:

  • Microsoft Visual Studio, Enterprise Edition 6.0
  • Microsoft Visual Studio 6.0 SP1
  • Microsoft Visual Studio 6.0 SP2
  • Microsoft Visual Studio 6.0 SP3
  • Microsoft Visual Basic Enterprise Edition for Windows 6.0
  • Microsoft Visual Basic Enterprise Edition for Windows 6.0 SP3
This article was previously published under Q267284

SYMPTOMS

When you attempt to open a non-local Microsoft Access repository database in Visual Component Manager (VCM) by specifying the share name that points to it, the following error message is generated on Microsoft Windows 95 and Microsoft Windows 98 computers:
Method '~' of object '~' Failed
If Visual Studio 6.0 Service Packs 3 or 4 have been applied, a dialog box with the following message is displayed:
Error: Installing Model File

RESOLUTION

Do not specify a share name in the Open Access Type Database dialog box. Map a network drive on the local computer to the share on which the Access database file (.mdb) is located, and then point to the mapped drive and folder that contains the database to open the non-local Access repository.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Open Visual Component Manager in Visual Basic 6.0.
  2. On the root VCM element, right-click to select Repository, select Open, and then select Microsoft Access Database (MDB).
  3. Specify the full path to the Access database on the non-local share. For example, \\testserver\testfolder\test.mdb.
  4. Click Open, and then click OK in the Visual Component Managers 6 tables do not exist in this database, add them? dialog box.
  5. The expected behavior is that the six VCM tables are added to the specified database and that the database is opened successfully. However, on a Windows 95 or Windows 98 computer, the errors specified in the "Symptoms" section of this article are generated.
The easiest workaround to address these errors is to map the share to a network drive on a Windows 95 or Windows 98 computer and point to the database by specifying the fully qualified path name with the mapped drive.
Modification Type:MinorLast Reviewed:8/15/2005
Keywords:kbBug kbpending KB267284
©2004 Microsoft Corporation. All rights reserved.