|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
SlickEdit: Code in over 40 languages across 7 platforms. SlickEdit’s unmatched power, speed, and flexibility allows even the most accomplished developers to write better code faster. Download a free trial today! |
|
#1
|
|||
|
|||
|
ADO password problem
I am developing a database program using ADO in VB6. I am using access 2000 to set up the database and Jet4.0 as the database engine, I have the latest service pack installed.
I have entered a password protection to my database file and then changed the connection string of my ADO component. After I modified it I got this message: Title: ADO component name body: Could not start your application. The workgroup information file is missing or opened exclusively by another user. why this problem is caused and who do I get rud of it? here is the code that worked before the the password was set: adoemployee.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\employee.mdb;Persist Security Info=False" and here is the modified code: Provider=Microsoft.Jet.OLEDB.4.0;Data Source==" & App.Path & "\employee.mdb;Mode=Share Deny Read|Share Deny Write;Persist Security Info=False;pwd=12345" Ive olso tried database password instead of pwd but I still got that annoying error. Pls help. |
|
#2
|
|||
|
|||
|
Try this instead
adoemployee..mode = adModeShareExclusive adoemployee.ConnectionString="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\employee.mdb;Persist Security Info=False;User Id =<username>;Password=12345" Last edited by saxtonj : September 16th, 2003 at 09:40 AM. |
|
#3
|
|||
|
|||
|
This is a good idea but I dont know what the User Id is or how to use it.
|
|
#4
|
|||
|
|||
|
Yes!tom_meir Need the userid & password!
|
|
#5
|
|||
|
|||
|
so how do I get the userId assuming the program will run on a different computer with different users then I. (or is the user ID related to the database instead of the computer Im working on?)
|
|
#6
|
|||
|
|||
|
The user ID in this case is associated with the database. The default user for an access database is I think admin but you can add other user/password combinations to your database.
If you don't recall setting a username when you added the password to the db try admin |
|
#7
|
|||
|
|||
|
Done. but now I get a different kind of error:
Could not find installable ISAM. Ive got the latest service pack and access 2000 pro and Microsoft Data Access Components (MDAC) 2.8. I have no Idea what Im doing wrong... |
|
#8
|
|||
|
|||
|
This is a Microsoft Knowledge Base Article - 209805
If you try to import, to export, or to link a file by using an indexed sequential access method (ISAM) driver, you may receive an error message if Microsoft Access cannot find the ISAM driver. You may also receive the following error message if you try to open an .xls file from Microsoft Access 95 (version 7.0) when the spreadsheet has been saved in a Microsoft Access 97 or an Access 2000 format: The wizard is unable to access information in the file '<pathname>'. Please check that the file exists and is the correct format. You may also receive this error message if you are trying to import from, link to, and export to Microsoft FoxPro from Access 2000. Access 2000 requires the use of the Visual FoxPro Open Database Connectivity (ODBC) driver. Microsoft Access 97 uses an ISAM driver. CAUSE ISAM drivers are used by Access to update file formats other than its own. If the path to the ISAM driver in your Windows Registry is not valid, or if the ISAM driver does not exist, you may receive the following error messages: Could not find installable ISAM -or- The wizard is unable to access information in the file '<pathname>'. Please check that the file exists and that the file is in the correct format. RESOLUTION To correct the problem, you can try to register the file manually or you must correct path name errors in the Windows Registry, and then install or replace the problem file. In the case of the first error message, the file name is directly related to the attempted operation. In the case of the second error message, the file name is mentioned in the text of the message. Locate the relevant file in the following table:File Name Import/Export ISAM for: Windows Registry Msexcl40.dll Microsoft Excel HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel Msexch40.dll Microsoft Exchange HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Exchange Msrd2x40.dll Microsoft Jet 2.x HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 2.x Msrd3x40.dll Microsoft Jet 3.x HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 3.x Msltus40.dll Lotus 1-2-3 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Lotus Mspbde40.dll Imprise Paradox HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Paradox Mstext40.dll Text HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Text Msxbde40.dll dBase HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Xbase Use Microsoft Windows Explorer to search for the file. If the file is found, record the path name for the file. If the file is not found, go to step 13. Open the Windows Registry Editor. WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. Move to the registry subkey that is described in the table, and then check the path name against the actual path name. If the registry key does not exist, go to step 8. Correct the path name if it is incorrect. Continue with these steps if it is correct. Close Registry Editor. If you changed the path name, repeat the process that produced the original error. If the error persists, try to manually register the file by using the Regsvr32.exe utility. Regsvr32.exe is an application that is used to register dynamic-link libraries (DLLs) and ActiveX controls in the Windows registry. You can use this file to stop the issue of mismatched .dll files. To start to re-register your .dll files by using Regsvr32.exe go to the next step. Verify that the Regsvr32.exe file is in the system folder where Windows is installed, for example: C:\Windows\System -or- C:\Winnt\System32 Click Start, and then click Run. In the Run dialog box, type the following command in the Open list. NOTE: The path to Regsvr32.exe and the name and the path of the DLL may be different on your computer. The following example command registers the Excel ISAM: Regsvr32 c:\winnt\system32\msexcl40.dllNOTE: Another method of registering DLLs is to use Windows Explorer to find the DLL. Double-click the DLL. In the Open With dialog box click to select Regsvr32.exe and then click OK. This creates a permanent association of all DLLs with Regsvr32.exe. You can easily register other unregistered DLLs by double-clicking them. For additional information about how to obtain this file, click the article number below to view the article in the Microsoft Knowledge Base: 267279 ACC2000: Regsv32a.exe Available in Download Center If the error persists, or if the path name was correct in step 5, rename the file. Start the Add/Remove Programs tool, start the Office 2000 Setup program, and then click to select the Repair Office option. -------------------------------------------------------------------------------- Take A Minute And Share Your Problem Or Solution With The Community! |
|
#9
|
|||
|
|||
|
Seen it. followed its "instructions", doesnt help either.
|
|
#10
|
|||
|
|||
|
Try installing the latest ADO drivers from www.microsoft.com/data
Make sure you get the Jet drivers, they are in a separate download from the MDAC file. |
![]() |
| Viewing: Dev Shed Forums > Programming Languages - More > Visual Basic Programming > ADO password problem |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|