OLB Reference a user does not have.

[Zeroanarchy]

In my VB app I have a reference to Microsoft Outlook 10.0 object library.

The file is located in: c:\program files\office2000\office10\MSOUTL.OLB

problem the person using the app does not have office2000. If I send the user a copy of the OLB file and told him to place it in any directory, how will VB find the file. Do you have to register the file somewhere? or do I have to register the new reference at the code??

Anyone got any ideas how the reference system works and how I might be able to solve this prob.

Thanks

Zero Anarchy

 

[johnwm]

regsvr32 will register .olb files

Check in your license agreement to see if MSOUTL.OLB is on your redistributable list Let me know if this helps
________________________________________________________________
If you are worried about how to post, please check out FAQ222-2244 first

'There are 10 kinds of people in the world: those who understand binary, and those who don't.'

 

[Zeroanarchy]

johnwm thanks for that I tried this before I posted the thread to find that it would not work on my system, I got the following error:

c:\progra~1\office2000\office10\msoutl.olb was loaded,but the dllregisterServer entry point was not found.

c:\progra~1\office2000\office10\msoutl.olb does not appear to be a .DLL or .OCX file

I was trying to avoid giving the user the wrong info and having to go back to the drawing board to work out what was the cause.

Thanks Zero

 

[SeeThru]

It does not seem possible to register OLB files manually - they have to be registered during application installtion.

Find out which version email program they are using and see if you can use that.

 

[strongm]

Er ... an OLB is a type library. Technically you don't need to redistribute (and therefore register) type libraries with your application; they are only needed on the development machine.

And even if you could (and actually you can, but not the way you are trying to do it) it wouldn't do any good. In your case your application has a dependency on Outlook 2000 being installed, and getting the OLB onto the target machine won't help (the OLB merely describes Outlook COM interfaces in terms that VB can understand - terms that get compiled into the application, which is why you don't need the type library on the target machine - but if Outlook itself is missing then there is nothing for VB to actually talk to ...)

 

[mattKnight]

maybe after 3 years ZeroAnarchy has found a solution...

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[strongm]

oops ...