Run-time Error '3633'

Messages postés
30
Date d'inscription
mardi 22 juin 2004
Dernière intervention
27 décembre 2004
- - Dernière réponse : cs_RL
Messages postés
30
Date d'inscription
mardi 22 juin 2004
Dernière intervention
27 décembre 2004
- 23 juil. 2004 à 10:53
Bonjour

Mon Pb concerne un programme ecrit en VB6 avec utilisation de l'assistant d'installation VB6.

J'ai installé ce programme sur plusieurs PC ( avec NT4 et XP français), mais sur un PC avec NT4 version Anglaise j'ai , lors de l'exécution de l'instruction : Set WK= CreateWorkspace("", "admin", "", dbUseJet) ( création d'un Workspace) le méssage d'erreur suivant: Run-time Error '3633'.

MS préconise d'insérer dans les Dll (lors de l'utilisation de l'assistant d'empaquetage) Msjet35.dll. J'ai fait la manip : Rein changé. Pire si je rajoute Msjet35.dll à l'installation de mon programme, lors de la désinstallation il est supprimé .... Access de fonctionne plus??

Je pencherais plutot vers un Pb concernant Dao360.dll mais je ne sais pas quoi faire
Merci à celui qui me donnera les bons tuyaux.
Afficher la suite 

4 réponses

Messages postés
4172
Date d'inscription
mercredi 30 juillet 2003
Dernière intervention
9 juin 2006
0
Merci
Voici un extrait du MSDN sur la runtime error 3633
PRB: App Generates Run-Time Error 3633 When Run on New Machine
Last reviewed: October 2, 1997
Article ID: Q174488  
The information in this article applies to: 
Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 5.0 

SYMPTOMS
When building setup disks for a Jet-based database application with the Setup Wizard, the Setup Wizard doesn't include the Microsoft Jet database engine files. When you install the application and try to run it, you get the following error: 

   Run-time error '3633':
   Can't load DLL 'MSJET35.DLL'

CAUSE
The Setup Wizard doesn't know to add the Microsoft Jet database engine if you are using the Microsoft DAO 2.5/3.5 Compatibility Library instead of the Microsoft DAO 3.5 Object Library. 

RESOLUTION
Use one of the two following methods to resolve this problem: 

Method 1

Open the project and on the Project menu, click References. 
2. Clear the Microsoft DAO 2.5/3.5 Compatibility Library and select the 
   Microsoft DAO 3.5 Object Library.

3. Click OK. 4. Save the project. 5. Return to References, switch the object libraries back again (that is, 
   do the reverse of what was instructed in step 2 above), and resave the
   project.

6. In the Setup Wizard - ActiveX Server Components pane of the Setup 
   Wizard, click Add Local, and add MSJET35.DLL from your Windows\System
   directory (Windows 95) or Windows\System32 directory (Windows NT). This
   process adds the Microsoft Jet 3.5 database engine and its supporting
   files.

NOTE: Adding MSJET35.DLL does not resolve the problem if the project has never had a reference to the Microsoft DAO 3.5 Object Library. 

Method 2
Use the Microsoft DAO 3.5 Object Library instead. 

STATUS
Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. 

MORE INFORMATION

Steps to Reproduce Behavior

Create a new application and add a reference to the Microsoft DAO 2.5/3.5 Compatibility Library. 
2. Create setup disks using the Setup Wizard. 3. Install the application on a new machine (that does not already have Jet 
   installed).

4. Run the application and note the error message. 5. Repeat the above steps, but add a reference to the Microsoft DAO 3.5 
   Object Library. The application should run correctly.

Examine the SETUP.LST file of the second application and note that it includes the following required files that the first application does not include: 

   MSJET35.DLL
   VBAJet32.dll
   VB5DB.dll

 


En suivant pas à pas ce qu'il indique, généralement cela passe.
A toi de tester

Christophe R.
Messages postés
30
Date d'inscription
mardi 22 juin 2004
Dernière intervention
27 décembre 2004
0
Merci
J'utilise plutôt la 2eme méthode qui préconise d'utiliser DA03.5, mais j'utilise DAO3.6 qui, je crois permet de travailler avec Access 2000 alors que DAO3.5 ne le peut pas.

Cela ne marche toujours pas.

Faut-il obligatoirement utiliser DA3.5? Je suis septique.

A propos,l'article MSDN concerne VB5, j'utilise VB6.
Cela peut-il expliquer que les méthodes ne fonctionnent pas?

Merci de votre réponse
Messages postés
4172
Date d'inscription
mercredi 30 juillet 2003
Dernière intervention
9 juin 2006
0
Merci
Un nouvel extrait du msdn concernant VB6
PRB: Visual Basic 6.0 Application Generates Run-Time Error 3633 When It Is Run on a New Computer
View products that this article applies to.
This article was previously published under Q280513 
SYMPTOMS
When you build setup disks for a Microsoft Jet-based database application with the Package and Deployment Wizard (PDW), the Package and Deployment Wizard does not include the Microsoft Jet database engine files. When you install the application and try to run it, you get the following error message: 

Run-time error '3633' 
CAUSE
The Package and Deployment Wizard does not know to add the Microsoft Jet 4.0 database engine if you are using the Microsoft DAO 3.6 Object Library. 
RESOLUTION
Add the MDAC_TYP.EXE to your setup package. 

NOTE: MDAC 2.6 and later no longer include the Jet engine. If you are using MDAC 2.6 or higher, you need to use the Jet redistribution pack. 

For more information about downloading the Jet redistribution for use with your application, see the following Microsoft Web site at: 

http://msdn.microsoft.com/dataaccess
MORE INFORMATION
This problem does not occur on Windows 2000-based computers or computers that have Microsoft Office 2000 installed. To reproduce the problem, install the following application that is created on a clean installation of Microsoft Windows 98, Microsoft Windows 95. or Microsoft Windows NT 4.0 SP3. 
Steps to Reproduce Behavior
Create a new application and add a reference to the Microsoft DAO 3.6 Object Library.
Create setup disks by using the Package and Deployment Wizard.
Install the application on a new computer that does not already have Jet installed.
Run the application, and note that you receive the error message.
Repeat the preceding steps, but add a reference to the Microsoft DAO 3.5 Object Library. Note that the application runs correctly. 
REFERENCES
For more information about Jet 4.0 and DAO 3.6, see the following MSDN Web site at:


Il faut visiblement installer MDAC_TYP sur le poste

et en voici un deuxieme
PRB: Error Message 3633 "Can't Load DLL '?????L?' " When Running Deployed Application
View products that this article applies to.
This article was previously published under Q260369 
SYMPTOMS
When you deploy an application that uses the CreateWorkspace method to create an Open Database Connectivity (ODBC) WorkSpace, the application raises one of the following errors: 

Run-time Error '3633' Can't load DLL "?????L?" 

-or- 

Run-time Error '3633' Can't load DLL "MSRDO20.DLL" 
CAUSE
When the call to CreateWorkspace creates an ODBC WorkSpace, it uses ODBCDirect, which is dependent on the Remote Data Objects (RDO) Msrdo20.dll file. Because there is no actual Reference to ODBCDirect in the project (just the type of call that is made in code), the Package & Deployment Wizard (PDW) does not know to include the Msrdo20.dll file. 
RESOLUTION
Add the Msrdo20.dll file to the Package. There are two different methods to accomplish this when running the PDW: 
If you are presented with a DAO Drivers screen, move ODBCDirect over to the Included Drivers column. This includes the Msrdo20.dll file.

From the Included Files screen, click the Add button and manually add the Msrdo20.dll file to the Package.
From the Included Files screen, click the Add button and manually add the Msrdo20.dll file to the Package.
STATUS
This behavior is by design.


Ici, il faut ajouter msrdo20.dll au package

Christophe R.
Messages postés
30
Date d'inscription
mardi 22 juin 2004
Dernière intervention
27 décembre 2004
0
Merci
J'ai installé Microsoft Jet 4.0 au lieu de Jet 3.5 pour NT4 et cela marche.

MDAC_TYP me paraît inutile car je n'utilise pas ADO

Une semaine de perdue dans l'enfer des DLL. Merci Bill.....

Je vous remercie infiniment pour vos informations

Vous n'êtes pas encore membre ?

inscrivez-vous, c'est gratuit et ça prend moins d'une minute !

Les membres obtiennent plus de réponses que les utilisateurs anonymes.

Le fait d'être membre vous permet d'avoir un suivi détaillé de vos demandes et codes sources.

Le fait d'être membre vous permet d'avoir des options supplémentaires.