executables still good, but code gone bad

[EvilOne]

I'm using VB6.0 professional. I've created and distributed numerous apps using RDO. The executables still run fine, but I am now receiving errors while I'm in the project:

When trying to Run/Debug Code - "Runtime error 429 : ActiveX Component can't create object"

When trying to Recompile(make the .exe) - "Compile Error: Permission Denied"

The MS Remote Data Object 2.0 is referenced in the project. I've uninstalled & reinstalled vb, but to no avail.

I downloaded the fix 'VB6cli.exe' from the MS website that addresses both symptoms, it executed sucessfully, however, the problems still exist.

The following code is what I've used all year to debug, compile and distribute apps. What happened??!!

Dim AS400cn As rdoConnection 'debug yellows this line
Dim AS400en As rdoEnvironment
Dim AS400conn As String

Set AS400en = rdoEnvironments(0)
AS400conn = "DSN=lnew400;UID=;PWD=;"
Set AS400cn = AS400en.OpenConnection("",rdDriverCompleteRequired, False, AS400conn)

Thanks in advance for your thoughts :0)

[filburt1]

A common control (i.e., OCX) is probably in use or needs to be re-registered. Either that, or a version for a reference is out of date (VB acts freaky when that happens).

[EvilOne]

What do you mean by 'a version for a reference is out of date?' and, Is there any resolution for this??

I have a feeling it's not a control issue. I tried my project out on someoneelse's pc with vb6.0 professional and got the same errors. I have to wonder if it's something to do with the professional version.

[EvilOne]

Resolution... After spending way too much time troubleshooting this problem, I broke down and ordered the enterprise edition. Uninstalled v6.0 professional, installed v6.0 enterprise and wouldn't you know it, problems disappeared.

What triggered the problems to suddenly begin - I still have no idea. There's something hokey going on with professional and RDO, as I've seen others reporting similar issues in this forum.

Good luck to those of you who also get tripped up by professional!!

Thanks

[noble]

yeah Bill did something with the professional edition that
makes it highly gay.

A friend of mine passed me his code to test after
spending hours of troubleshooting the same problem. I found
that it compiled successfully under my VB but on his
computer, he wasn't able to compile the program and even
with the compiled version (that ran fine on my computer)
woulnd't run on his. What the program did was shell an
instance of MSWord. We were both running win2k and vb6.

Are you running Win2k? Maybe it's not professional and
it's something that Win2k installed.

[EvilOne]

I'm running Windows NT.

During my troubshooting I had loaded the 6.0 professional version on Win98 and another NT pc - had the same problem everywhere. I did try it on WinME, however, with the 6.0 enterprise - had no problems there.

I really have a feeling that professional is lacking something that RDO programs need!!

Oh well, my company paid for the enterprise edition and I'm up and running again. Happy Codeing!!