Installing Using OLD OLEPRO32.dll

Printable View

Dec 11th, 2006, 09:13 AM
jesus4u

Installing Using OLD OLEPRO32.dll

Question:

If I am installing my vb6 app on a Windows 2000 Server, and I deploy these files olepro32.dll (6/19/2003), oleaut32.dll (6/19/2003), and msv6vm60.dll (6/19/2003), and their dates are old, will this cause a problem with my application from running correctly?

thanks

Alex
Dec 11th, 2006, 10:49 AM
Hack

Re: Installing Using OLD OLEPRO32.dll

The best way to determine this is to install it on a test box, run it, and see what happens.
Dec 11th, 2006, 11:34 AM
RhinoBull

Re: Installing Using OLD OLEPRO32.dll

I don't think they will cause any troubles at all - I haven't come across any issue in any post NT4 OSs.
But as Hack said it's always a good idea to test.
Dec 11th, 2006, 12:12 PM
jesus4u

Re: Installing Using OLD OLEPRO32.dll

ok, comments noted...thanks... Now, another question centered around this topic.

I tried reinstalling the stdole2 component and the Wise installer said that the component was locked. How do I get around this one?
Dec 11th, 2006, 12:23 PM
Hack

Re: Installing Using OLD OLEPRO32.dll

Locked from with in the installation package, or locked as "in use" on the machine itself?
Dec 11th, 2006, 12:42 PM
Pradeep1210

Re: Installing Using OLD OLEPRO32.dll

I think it needs to be ignored. Don't install it if it's already present on the system.

Pradeep :)
Dec 11th, 2006, 01:54 PM
jesus4u

Re: Installing Using OLD OLEPRO32.dll

Quote:

Originally Posted by Hack

Locked from with in the installation package, or locked as "in use" on the machine itself?

...machine itself
Dec 11th, 2006, 01:55 PM
jesus4u

Re: Installing Using OLD OLEPRO32.dll

Quote:

Originally Posted by Pradeep1210

I think it needs to be ignored. Don't install it if it's already present on the system.

Pradeep :)

That is what brings up the original question. If I am upgrading my app which was originally compiled in vb5 then recompile in vb6. Do I need to reinstall these core components?

Thanks
Dec 11th, 2006, 02:09 PM
RhinoBull

Re: Installing Using OLD OLEPRO32.dll

Quote:

Originally Posted by jesus4u

... was originally compiled in vb5 then recompile in vb6. Do I need to reinstall these core components?

That's the main key which you should've mentioned from the beginning.
So, the answer is YES, YES and YES.
Dec 11th, 2006, 02:12 PM
jesus4u

Re: Installing Using OLD OLEPRO32.dll

Quote:

Originally Posted by RhinoBull

That's the main key which you should've mentioned from the beginning.
So, the answer is YES, YES and YES.

ok that is what I thought but again how to update the core files if the OS has them locked?
Dec 12th, 2006, 07:09 AM
Hack

Re: Installing Using OLD OLEPRO32.dll

Typically during an installation you will get a message box indicating that [this file] with [this date/time stamp] is going to be replaced with [that file] with [that date/time stamp] and you will be asked if you wish to proceed.

Is this happening?
Dec 12th, 2006, 07:50 AM
jesus4u

Re: Installing Using OLD OLEPRO32.dll

Quote:

Originally Posted by Hack

Is this happening?

No it is not! I am using the Wise installer pro edition and you would think the default behavior of the installer would be to prompt you as you suggest but it just errors out and quits. I did some research and found out that I can force Wise to install "in use" files by applying a certain attribute in Wise. So I am trying that today and will let you know.

anyone else have experience using Wise?

All times are GMT -5. The time now is 07:45 PM.