>I am struggling to register a DLL on client PCs. The clients are all W7 SP1 32 bit.
>
>My main application is located in and runs from C:\localapps\. (This gets copied from a network drive if a newer version is on the network). I have copied mynew.dll into the localapps folder on the clients; I have also copied the tlb and the vbr files - I was not sure if these were needed or not - could someone advise on this point?
>
>When running 'regsvr32 c:\localapps\mynew.dll' at the command line prompt I get errors:
>
>On one W7 client the error states: "The modul "c:\localapps\mynew.dll" was loaded but the call to DllRegisterServer failed with error code 0x80004005".
>
>On another W7 client I get "The module 'c:\localapps\mynew.dll' failed to load. Make sure the binary is stored at the specified path or debug it to check for probles with the binary or dependent .dll files. The specified module could not be found".
>
>I also have the VFP9r.dll ,VFP9t.dll and VFP9RENU.dll in the c:\localapps folder.
>
>I have tried logging on to the client as both local and domain admin. I have also tried "Run as administrator" against the CMD prompt.
>
>I do not understand why I get different error messages on what appear to be 2 identically configured clients.
>
>Could someone shed some light on what I am missing?
>
>Thanks
>Barry Sutton.

On Vista forward, you must have administrative rights when manually registering a dll. In an installer that is recognized by Windows (tm), special rights are granted.

Start the cmd window as administrator, and then use regsvr32.dll to register the dll.

On x64, use regsvr32.dll from the SysWow64 directory. I think it's actually the same file (as contrasted with odbcad32 for setting up DSN's), but I always use it from there anyway on x64 systerms, just to be sure.

hth,

Hank