VB6Install on Vista 2

[Terabithia]

After doing some research, I decided to move forward with a install of VB6 SP6 on my new Vista system.

When VB starts it displays a Data View message that says "Automation error, Error accessing the OLE registry"

Any suggestions?

Thanks

 

[tedsmith]

Me too
Looks like you may have to face up to converting to VBnet! or even C Sharp!

 

[dpaulson]

Right click on the shortcut fdor vb6. Select properties. Select Compatibility tab. Check 'Run this program as administrator' in the Privilege level.

That all that I needed to do to run on vista.

David Paulson

 

[Terabithia]

David,

Thanks! That did the trick.

 

[dilettante]

Note that you may want to set the Compatability option to disable Aero for the VB6 IDE. Otherwise the Form Design view can be rather slow and jerky to use.

 

[HughLerwill]

Related Vista issues;

1. While a few tweaks may be required Sendkeys when used in an exe generally works as before (most problems reported seem to relate to beta versions of Vista) however it reliably produces an Error 70 for me when running a project in the IDE. The following overcomes that;

Sub Sendkeys(text$, Optional wait As Boolean = False)
'wrapper for Sendkeys which does not crash the IDE with an Error 70 under Windows Vista
CreateObject("WScript.Shell").Sendkeys text, wait
End Sub

I currently use a modified version of the above Sub so that VBA.Sendkeys is used in exes and WScript.Shell.Sendkeys is used when in the IDE.

A complete rework for Sendkeys (if it is required) appears to be available from

http://vb.mvps.org/,

I have not used it.

2. When compiling a project from the IDE always check the destination folder for the resulting exe file. Under XP and earlier the destination folder for the exe reliably reflected that in the .vbp file, in Vista I have found it does not. If you do not check, your exes may be saved to places you had not imagined.

 

[dilettante]

I suspect that a number of "mysterious" issues may be resolved by using an application manifest with the VB6 IDE. This bypasses the AppCompat shims (such as file/registry virtualization), which might be quite desireable - or not. It's hard to know exactly what conditions need to be in place when Microsoft says the VB6 IDE "works" in Vista.

Of course you wouldn't want the manifest to select Common Controls 6.0: The well-known problems of control rendering (opt-buttons within a frame, etc.) are clumsy to deal with when the IDE exhibits them in design mode.

Ultimately the most viable approach may be to move back to XP (or install VB6 within an XP VM under a Vista host OS). This doesn't prevent targeting Vista, though it all begins to make testing under the IDE clumsy to impractical to impossible.