Printable View
Dear Team i have developed an application using VB6 and dataenvironment and i m using MS access as database now i want to run this application on other PC how can i do this can anybody help me i tried with package & deployment wizard but in this case also it is not running on other pc.
waiting for response.
Thanks in advance.
What exactly do you mean by this? Are there errors, is it missing functionality? You will have to give us a lot more information if you want anybody to be able to help you.Quote:
but in this case also it is not running on other pc
Dear Team
i prepared my application and made the .exe also now i want my application to be run on another pc its like deployment as i said earlier i am also using MS access database and dataenvironment for reporting .when i am running the setup files at that time it is showing msgbox for updates for system files and asking for restart but after restart also same problem remains.
thats why i want to ask you the right procedure to deploy this kind of application.
Thanks in advance
Thread moved to the 'Application Deployment' forum, which is where questions about installing/distributing your software belong.
There is a link in the FAQs at the top of this forum which explains how to fix that.Quote:
when i am running the setup files at that time it is showing msgbox for updates for system files and asking for restart but after restart also same problem remains.
This symptom often means your package is trying to deploy operating system files that it shouldn't. Sometimes this can be a version of the VC++ runtime too.Quote:
Originally Posted by amitpanchal
The PDW is very old, and has never had much but critical updates made to it in service packs. In particular VB6DEP.INI will be far out of date, and this contains the base set of "rules" the PDW uses to decide what dependencies should or should not be deployed. These rules have changed a lot since VB6 came out in 1998. Some "new rules" are complicated, and vary by target OS so there is no easy fix using the PDW.
You have to either update VB6DEP.INI, which can be a daunting task, or carefully "uncheck" the not-to-be-deployed DLLs in the files list that appears in an early panel of the Wizard.
Posting your package's SETUP.LST may help us identify these DLLs for you. We don't need to see the comment lines at the end though (lots of XXXXXXXXXs).
And of course the problem may be something else.