[RESOLVED] Error 713 Obj Defined Error in Vista

Hi

I have an application working OK on all platforms other than Vista that uses VB Data Designers. It gives a run time error 713 Object Defined Error when I try to run it.
So I have a created very short cut down version that just tries to connect through a DD to a database. To trace the problem the first line of code that actually runs is

Msgbox Detest.Conn1.Version

(where Detest is the name of the Data Env and Conn1 is the name of the connection).

I have placed a msgbox in the Initialise Event if the DD but it does not even get that far so I can only assume it is not even initialising.

I have tried installing it using PDW and I have tried running it as Administrator in Vista. I have registered msado15.dl (as it uses ADO 2.8) as Administrator - this is the only related dll listed in the References section of the IDE.

I have also registered msde.dll and msderun.dll as Administrator together with several others dll's that have been suggested through some other postings but it still will not run.

Does anyone have any suggestions, if I had any hair I would be pulling it out. Apologies if this should have been posted to another forum.

Thanks

You shouldnot be deploying MDAC components ever, especially on Vista. You should be deploying the while MDAC except on Vista. As I would image you probably have made other such mistakes which prevent you from deploying properly on Vista (and other OS versions).

Hi Randem

Thanks for the response.

Can I just be clear what you mean.

When I produce an install package I should not include any MDAC files with the package so these should be specifically excluded when prompted by the PDW.

Are there any other files that I should exclude or is there anywhere that lists this information.

Thanks again.

PDW does it wrong. You need to include the whole MDAC not just some of the files that are included in the MDAC. Yes, there is a list but you won't find it here and I am not allowed to tell you where it is on this forum... It's more like a list of files that you should not include...

Just to keep the post updated and hopefully this info will help someone else.

I did eventually resolve this issue with the pointer from Randem to the reason.

The solution was to register a list of dll's etc. that are supported by Vista for VB but not actually "installed" / "shipped". As a precaution I unregistered them first and re-registered them. I did this using a batch file I created which I ran as Administrator.

One other thing was a problem with RICHTX32.OCX this was corrupt on the system so I replaced it with an alternative version which actually had a slightly earlier version number so I don't know if there is an issue with the one that ships with Vista, anyway it fixed my problem.

I hope this may help someone.