Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
OLE server not registered
Message
De
17/05/1999 11:39:05
 
 
À
17/05/1999 10:53:38
Information générale
Forum:
Visual Basic
Catégorie:
Contrôles ActiveX
Divers
Thread ID:
00202167
Message ID:
00219632
Vues:
32
>>>>I was wondering if you could help me. When I try to register my exe, I get an error like this:
>>>>
>>>>LoadLibrary(".... my-ocx-here...") has failed.
>>>>GetLastError returns 0x00000485.
>>>>
>>>
>>>Typically, this indicates that one or more files that the OCX depends on are not present on the system, or not yet registered. You'll need to check what files (typically, system .DLLs) are needed, and at what version, to make sure they're present before you try to register the OCX.
>>>
>>>>Any ideas? I'm using long file names, should that matter?
>>>>
>>>>>Did you register the OCX after changes?
>>>>>(i.e. regsvr32 ur-ocx-here )
>>
>>
>>Let me start over. I've got a VB application. I want to register one of the VB objects as a COM component for use in an Access application. How do I do this?
>>
>
>You can use REGSVR32 as shown above, however, if you have simply copied the file to a target system, there may be other components needed on the target system in addition to the .DLL or .EXE file containing your COM Server; that's exactly what is indicated by the error 485 - there's something needed by your OCX (an OCX is really just a renamed .DLL) in order to even load. You can use the DEPENDS utility to determine what external functions (.DLL entrypoints, other COM Servers, etc.) are needed, and you'll have to adjust your installation procedure to ensure that they are present and available on any target system using the OCX.
>
>>Also, where can I find documentation on regsvr32 and the various parameters it takes?
>
>If you issue the command REGSVR32 /?, it will display a message box with the information. The command line switches (there are 5) are:
>
>/u - unregister server
>/s - Silent (does not display message box on success)
>/c - console output
>/i - pass an optional commandline to DllInstall or DLLUninstall (with /u)
>/n - do not call DllRegisterServer; use only with /i


You are being very helpful and patient. Thank you.

What is a DEPENDS utility? where? how?
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform