The app is fine on SP2. It allegedly has problems on XP machines without SP2. Even on a non-Sp2 machine the app can be executed but crashes at certain points once it has been started.
Main Topics
Browse All TopicsI have an app written using VB 6.0 SP6. My development machine is running Windows XP Home with Service Pack 2. I generate the .EXE and pass it on to the installers. They are reporting problems on machines that are running Windows XP without Service Pack 2. Apparently at a certain point beyond the initial login and menu the app cancels. The installers have reported 'phantom' problems in the past so I am sceptical. They are supposed to send me the exact error messages but even before I get that I'm wondering if this should be a problem? I don't know if this matters but In the refences section of my project I have:
Visual Basic for Applications
Visual Basic Runtime objects and Procedures
Visual Basic objects and procedures
OLE Automation
Microsoft Scripting Runtime
Microsoft Script Control 1.0
Microsoft Data Formatting Object Library 6.0 (SP6)
Microsoft Data Report Designer 6.0 (SP4)
Microsoft Data Environment Instance 1.0 (SP4)
Microsoft Active X Data Objects 2.5 Library
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Most likely your installers didn't include all the updated files to run the program... most importantly the MDAC needs to be the same, or newer, version on the client machine.
You can verify what version of the MDAC is installed on your test machine by viewing the Administrative Tools -> ODBC Connections -> About tab in that machine.
I have seen this issue pop up quite often, and it's just "build and test" until it works completely...PS Images are a nice way to avoid re-installing the machine.
Good luck.
It is most likely that they did not include the control in their installation package; however, here is another problem that people run into with InstallShield Express.
One thing that it might be is that they did not include the dialog that asks if you want to install this for a single user or for everyone on the machine. If you run your installation and it does not show that dialog then it is likely that it is defaulting to single user installation. Then if someone installs it as Admin on a multiple user system those controls will only be registered for the Admin user and not for any other users. That would mean that any other users of the system will get Error Number 339 for those controls.
Business Accounts
Answer for Membership
by: Marv-inPosted on 2004-11-18 at 16:03:38ID: 12620602
sp2 has a firewall built-in - i would make sure your app isnt blocked