Results 1 to 5 of 5

Thread: Change ActiveX Data Objects 2.5 to 2.0!!!

  1. #1

    Thread Starter
    Hyperactive Member
    Join Date
    Jan 2000
    Location
    London
    Posts
    290
    I cant do it!

    I go to references, uncheck 2.5, check 2.0, save.
    I can look at the .vbp file and see my change. When i next go into visual basic, its put it back to 2.5, even though i unchecked `upgrade activex` on the properties page.

    I dont want 2.5 on this project, as i dont want 7megs of mdac_typ.

    Any ideas? I`m using visual basic 6, service pack 4, on windows 98 se. (This worked ok before i got service pack 4, btw)

    Thanks,
    alex.

  2. #2
    Lively Member Dr_Evil's Avatar
    Join Date
    Mar 2000
    Location
    Columbus, OH
    Posts
    105
    Not to insult anyone's intelligence but did you save your project after making the changes to your references? It's a common mistake so check that first. If that doesn't fix it then repost & I'll see what I can do...
    Dr_Evil
    Senior Programmer
    VS6 EE
    VS.NET EA

  3. #3

    Thread Starter
    Hyperactive Member
    Join Date
    Jan 2000
    Location
    London
    Posts
    290
    no, i`m not insulted, but i have saved.
    Try it. Assuming you have service pack 4 (if you dont this wont be a problem to you), change from 2.5 to 2.0 (ie uncheck 2.5, and check 2.0). Save. Quit. Maybe look at your projects .vbp file. Then just load up vb, load your project and then quit. You`ll be asked if you want to save changes. If you do it`ll change your project. With 2.0 selected your project file will use msado20.tlb, with 2.5 it`ll use msado15.dll.
    Very strange!
    alex.

  4. #4
    Lively Member
    Join Date
    Jul 2000
    Location
    Australia
    Posts
    69
    Aha!

    I had the same problem today same issue, after installing SP4.


    Gerard

  5. #5

    Thread Starter
    Hyperactive Member
    Join Date
    Jan 2000
    Location
    London
    Posts
    290
    Well, its august 1st today, i heard that service pack 4 will be on the msdn disks this month, so i imagine there`ll be a lot of p**sed off users unless someone who understands what is going on (at microsoft perhaps, that`d be nice) produces a guide. Or warns people not to install the patch if they want to continue developing old software without the need to perform a serious upgrade to the os that involves a reboot (ie something you cant do when you are updating software remotely).

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