Re: Big VB6/Pro problen on XP/SP2- bzw. WINDOWS 2003 server- systems

Tech-Archive recommends: Speed Up your PC by fixing your registry

> The problem also exists, if I have the PDW create a new
> program-installation-pakage!

Not quite understand the rest of your message but I did have problems
installing a VB program packaged with PDW on an XP OS with repeated prompts
to reboot without success in installing. Then later on a dos window would
pop up for a split second and disappear. Again fail in installation.

In the end I was forced to look for a better installer and found Inno Setup
freeware works just fine. One must however note that Inno Setup does not
automatically code extract the required DLLs and OCXs. For that you need
supporting tools at Inno Setup site like Inno Script.

Worth a try ; not difficult to use at all.

Kay



"Winfried Kaiser" <w.kaiser_nospam_@xxxxxxxxxx> wrote in message
news:%23flHYOblFHA.2396@xxxxxxxxxxxxxxxxxxxxxxx
> I have installed our application on virgin XP/SP2- bzw. WINDOWS 2003
> Server-system, and do experience a big problem, that did not occur
onXP/SP1-
> or WINDOWS 2000 Server-systems!
>
> The problem-symptons indicate, that the problem occurs when trying to
access
> an ACCESS-MDB via DAO 3.6/JET 4.0, but it could as well be another
problem.
> (Why I cannot just debug the problem with VB6 will be explained now!)
>
> The very strange thing, however, is, that after installing VB6/Pro
> (CD-Version of 1998(!)) this problem is gone, and the programm happily
runs
> again (that's why I can't debug this f.... problem)! After de-installing
VB6
> the problem reappears.
>
> The problem also exists, if I have the PDW create a new
> program-installation-pakage!
>
> Has anybody else experienced this problem and/or jnows a solution for it?
>
> I have solved the problem using a "brute-force" approach (still hoping for
a
> more intelligent solution):
>
> From an installation supervision software I have gathered the information,
> which DLLs are installed on the virgin systems when installing VB6/Pro (58
> DLLs althogether).
>
> Using that info (and some wizardry) I had the PDW create an
> installation-package, which just contains and installs these DLLs.
>
> And after the additional installation of that package, our program feels
> happy again in these environments.
>
> I don't know why, but I could not care less, until a better solution comes
> up!
>
> --
> Dipl.-Ing.(TH) Winfried Kaiser
> c/o Fortune Systems GmbH & Co.
> Postfach1
>
> D-24975 Husby
> Germany
>
> Fon: (49)4634-746
>
> --
> Dipl.-Ing.(TH) Winfried Kaiser
> c/o Fortune Systems GmbH & Co.
> Postfach1
>
> D-24975 Husby
> Germany
>
> Fon: (49)4634-746
>
>
>
>
>
>
>


.

Relevant Pages

  • Re: Upgrade runtime-based application
    ... I seem to recall, that in A2000 PDW, that option installed a new "different ... Much like installing multiple versions of Office, ... in this case we only WANT "One of My App" in Add/Remove!!! ... from Add/Remove programs? ...
    (microsoft.public.access.devtoolkits)
  • Re: Packaging and Deployment Wizard - Access Violation - W98
    ... I encountered this situation and what was happening was PDW was ... creating a file that was the same name as the folder that the app ... was installing into and thus couldn't create folder as the name ... A better fix would be to get a real installer. ...
    (microsoft.public.vb.general.discussion)
  • Re: A2K to Access 2003 conversion and back again?
    ... if you installing your application on Access 2000 clients - then you have ... to convert your application back to Access 2000 (menu tools-database ... machine using the PDW. ...
    (microsoft.public.access.developers.toolkitode)
  • Re: A2K to Access 2003 conversion and back again?
    ... if you installing your application on Access 2000 clients - then you have to convert your application back to Access 2000 (menu tools-database utilities), and make MDE on Access 2000. ... machine using the PDW. ...
    (microsoft.public.access.developers.toolkitode)
  • Re: Error loadin VS 2005 DLLs in Windows Vista
    ... The scenario is a Legacy VC 6.0 application which we are adding new mixed ... mode DLLs compiled with VS 2005. ... Installing the Visual C++ 2005 Redistributable changes the error to: ... Have you tried a "Thinstall Solution"? ...
    (microsoft.public.vc.language)