[RESOLVED] Attn: MartinLiss

[BrailleSchool]

Hi:

I am checking out the registration program from the Code Bank from MartinLiss and I am getting an problem with a missing file. I recently had to uninstall and reinstall VB6 Enterprise Edition and I also installed VB6 SP6 but when I run the Protect, I have a problem with a reference. Screen shot attached. I have Office XP installed on this machine too. (I have no problems in running the KeyGen though)

Please advise

[RobDog888]

I havent seen it but it looks like it was written to send information via email. Martin probably used a reference to Outlook 98. You should just be able to remove it and add a new reference to your version of Outlook.

[RhinoBull]

Or use late binding instead so versioning wouldn't be an issue.

[BrailleSchool]

The version of Outlook I use is Outlook Express

[RobDog888]

Cant automate anything with Outlook Express as it doesnt expose any valid COM interfaces.

[dglienna]

You can get it from this page:

http://www.ascentive.com/support/new...me=STDOLE2.TLB

[RobDog888]

You can get it from this page:

http://www.ascentive.com/support/new...me=STDOLE2.TLB

You read the question wrong dglienna. The missing reference is Outlook and not the selected reference "OLE Automation".

[dglienna]

Oops. I thought it was pointing to the missing location

EDIT: Select "microsoft outlook 10.0 library" instead

[RobDog888]

I know, I had to read it twice to make sure I responded correctly.

Edit: Solution in post #2.

[BrailleSchool]

I havent seen it but it looks like it was written to send information via email. Martin probably used a reference to Outlook 98. You should just be able to remove it and add a new reference to your version of Outlook.

How? lol

[RhinoBull]

I know, I had to read it twice ...

I thought it was crystal clear...

I...Solution in post #2.

Nah, #3 is better... unless you meant reply #2 ...

[dglienna]

He didn't install Outlook when he loaded Office XP.

[BrailleSchool]

I thought it was crystal clear...


Nah, #3 is better... unless you meant reply #2 ...

checking for different versions might be the best solution because you never know who is using what.

[BrailleSchool]

He didn't install Outlook when he loaded Office XP.

thought i did but seems not. going to rectify that problem either tonight or tomorrow but would love to be able to check for different versions of outlook.

[MartinLiss]

I don't know why that reference is there since I use MAPI and not Outlook so you should be able to just remove it.

[dglienna]

rhino posted the answer to that one. use late binding to use the one that's installed.

[MartinLiss]

BTW if you want to get my attention, an email or PM is better.

[BrailleSchool]

BTW if you want to get my attention, an email or PM is better.

ok, ill remember that for the future

[RobDog888]

@RB, I thought I was clear. Post #2

Either way you can not rely on the user having Outlook.

[RhinoBull]

checking for different versions might be the best solution because you never know who is using what.

So that is why I suggested the "late binding".

[RhinoBull]

@RB, I thought I was clear. Post #2

Either way you can not rely on the user having Outlook.

That is true if user "category" is uknown - for corporate type user late binding is pretty much what's needed.

[BrailleSchool]

how would this be done?

[RhinoBull]

You would use CreateObject() function:

Dim objOutlook As Object
 
    Set objOutlook = CreateObject("Outlook.Application")
    'and so and so forth ...

[RobDog888]

And any Outlook constants need to be defined too or just use the equilivalent values.

[RhinoBull]

I usually use early binding in development - it's much easier to get all the properties.methods/const - once I'm done I would simply "switch" back to late binding and check off the references.

[BrailleSchool]

ill have to check out MSDN to find out what all these values would be. this is totally new to me.

[RhinoBull]

That might be a little difficult, though.
Here is what may try:
- (while in development) set references to MS Outlook
- declare all of your object variable as you would normally do (as Outlook.Aplication, etc)
- do your coding (intellisense will definitely help you to define all you need)
- when you done coding and everything works - turn off references and re-declare your object vars As Object
- use CreateObject function to create instance of Outlook.Application
- declare your own const using those values that Outlook has
- rest fo your code should remain unchanged

Good luck.

[BrailleSchool]

That might be a little difficult, though.
Here is what may try:
- (while in development) set references to MS Outlook
- declare all of your object variable as you would normally do (as Outlook.Aplication, etc)
- do your coding (intellisense will definitely help you to define all you need)
- when you done coding and everything works - turn off references and re-declare your object vars As Object
- use CreateObject function to create instance of Outlook.Application
- declare your own const using those values that Outlook has
- rest fo your code should remain unchanged

Good luck.

This seems to be overwhelming stuff for a newb like me, lol.

[MartinLiss]

This seems to be overwhelming stuff for a newb like me, lol.

But as I said above, you don't need to worry about it. Just remove the reference and I believe it will still work.