VB6 Application on XP or Vista... 1

[bluenoser337]

I'm the farthest thing from a VB expert but I did create some small applications VB6 (not VBA) for W2K systems a number of years ago. My questions are (1) will VB6 install on XP or Vista, (2) will my exe file run on XP or Vista with no changes (3) if #2 is "no", then is there a way to change or re-compile the source code to make this work? Any help or assistance appreciated!!

 

[johnwm]

I have had no particular problems installing and running VB6 under XP. The compiled programs also work fine. You may have some issues if you compile on a late machine and try to run the compiled app on an older OS

___________________________________________________________
If you want the best response to a question, please check out FAQ222-2244 first.
'If we're supposed to work in Hex, why have we only got A fingers?'
Drive a Steam Roller
Steam Engine Prints

 

[bluenoser337]

Tried just running my exe on an XP Pro SP2 system. The splash screen comes up and stays for the normal amount of time...then disappears and the application vanishes. Where to start.....

 

[JoeAtWork]

I've been running VB6 on XP Pro since at least 2005 and never had any issues whatsoever. Have you installed all the Service Packs for VB6 (I'm running on SP5, and I think there may even be SP6)?

 

[bluenoser337]

Joe....here's where my lack of knowledge shows through...I don't have VB installed on the machine I am trying to run the exe file that was created on a W2K system. I am trying to run the exe file only. Should I have to install VB6 to run the exe? Thanks!!

 

[Swi]

You need to package and deploy your application (or some other installer) so the dependencies get registered, etc...

Swi

 

[bluenoser337]

Swi....I guess I have some reading to do....thanks!

 

[Swi]

Just run the package and deployment wizard that comes with VB6 to create a setup program. It is pretty self explanitory.

Swi

 

[JoeAtWork]

I thought you meant running VB6 itself.

 

[bluenoser337]

Swi....that is just too cool....thanks!!!! Working A-1 on XP.

 

[dilettante]

PDW deployments work fine on Vista too... as long as the application was written to proper Windows standards. Which many are not.

The usual problem is encountered when trying to create files or write to files in App.Path, which is verboten and has been since at least Win2K. Only starting with Vista is this enforced rigorously. More specifically, Program Files is not a place to write data.

 

[bluenoser337]

Everything appears to be fine except the reporting. My original applications use the version of Crystal Reports that is included on the VB6 CD. The "Crystal Report Control 4.6" is checked in the component list, but clicking to generate a report does nothing...and doesn't generate any errors. Any thoughts on what I can look for? Thanks tons for the help so far!!!!

 

[bluenoser337]

Update....if I try to preview the report from the Crystal Reports designer first (it is version 4.61), I get the error "ODBC Server Driver [Numeric Value Out Of Range]".

 

[Golom]

Crystal Reports (now Business Objects) is currently around release 11 or 12. The old (somewhat brain damaged) 4.x version included with VB6 may not fare very well in XP or Vista because it was released in the Win95/98 era.

You may want to get your hands on a less antiquated version of Crystal (AKA Business Objects).

 

[Swi]

You could also use VB6's Data Reports if the reporting is not too involved. I have used Data Reports effectively on XP and Vista.

Swi

 

[dglienna]

Access 2007 includes the Crystal Reports designer and you can distribute the runtime & .rpt files.

-David
2006, 2007 & 2008 Microsoft Most Valuable Professional (VB)
2006 Dell Certified System Professional (CSP)

 

[BobRodes]

<Any thoughts on what I can look for?

I ran into a problem with porting Crystal Reports from a Win2000 machine to an XP. The reports themselves had been developed on the Win2000 machine, and wouldn't run on the XP machine. I was using version 8.something, not the one that ships with Visual Studio.

Anyway, I solved it by redoing the report files. It was simply (well, it wasn't simple to think of, since I hadn't yet developed my present cynical attitude) a matter of installing Crystal Reports on the XP box, opening up the old reports, and cutting and pasting everything into a new report definition. Perhaps this will work for you as well.

Good luck,

Bob