Results 1 to 12 of 12

Thread: Installing Using OLD OLEPRO32.dll

  1. #1

    Thread Starter
    PowerPoster
    Join Date
    Jan 2001
    Location
    Florida
    Posts
    3,216

    Question 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

  2. #2
    I'm about to be a PowerPoster! Hack's Avatar
    Join Date
    Aug 2001
    Location
    Searching for mendhak
    Posts
    58,333

    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.

  3. #3

  4. #4

    Thread Starter
    PowerPoster
    Join Date
    Jan 2001
    Location
    Florida
    Posts
    3,216

    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?

  5. #5
    I'm about to be a PowerPoster! Hack's Avatar
    Join Date
    Aug 2001
    Location
    Searching for mendhak
    Posts
    58,333

    Re: Installing Using OLD OLEPRO32.dll

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

  6. #6
    VB Addict Pradeep1210's Avatar
    Join Date
    Apr 2004
    Location
    Inside the CPU...
    Posts
    6,614

    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
    Pradeep, Microsoft MVP (Visual Basic)
    Please appreciate posts that have helped you by clicking icon on the left of the post.
    "A problem well stated is a problem half solved." — Charles F. Kettering

    Read articles on My Blog101 LINQ SamplesJSON ValidatorXML Schema Validator"How Do I" videos on MSDNVB.NET and C# ComparisonGood Coding PracticesVBForums Reputation SaverString EnumSuper Simple Tetris Game


    (2010-2013)
    NB: I do not answer coding questions via PM. If you want my help, then make a post and PM me it's link. If I can help, trust me I will...

  7. #7

    Thread Starter
    PowerPoster
    Join Date
    Jan 2001
    Location
    Florida
    Posts
    3,216

    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

  8. #8

    Thread Starter
    PowerPoster
    Join Date
    Jan 2001
    Location
    Florida
    Posts
    3,216

    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

  9. #9
    PowerPoster RhinoBull's Avatar
    Join Date
    Mar 2004
    Location
    New Amsterdam
    Posts
    24,132

    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.

  10. #10

    Thread Starter
    PowerPoster
    Join Date
    Jan 2001
    Location
    Florida
    Posts
    3,216

    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?

  11. #11
    I'm about to be a PowerPoster! Hack's Avatar
    Join Date
    Aug 2001
    Location
    Searching for mendhak
    Posts
    58,333

    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?

  12. #12

    Thread Starter
    PowerPoster
    Join Date
    Jan 2001
    Location
    Florida
    Posts
    3,216

    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?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width