B
BobS
I have previously distributed my Access97-based Asset Management Program
with the Office 97 Developer Edition.
It was setup with Setup Wizard, and included 64 other files, including
..exe, .dll, .ocx, .stf, .tlb, and many other Windows files.
It has worked fine until XP.
The problem seems that XP can't find system.mdw. XP (and 2000?) stores the
system.mdw file in a different folder than does Windows 98 and previous.
But, the Setup Wizard will not let you change the destination of a system
file in the setup. (I hear that third party setup programs allow this.)
I have updated my Access97-based Asset Management Program to Access 2000 to
better run on 2000 and XP, which expect some .dll files to be in different
folders.
I would now like to package and distribute my program (.mde) as before, but
with Office 2000 Developer.
BUT I can't get there.
When I open the Package and Deploy Wizard from the start menu, it says to
open the P&D Wizard from within the VBA Solutions project. I have only the
Access-based .mde file to begin the setup, and no .exe for the VB6.
Where do I start?
Thanks for the reply,
Bob Sub
with the Office 97 Developer Edition.
It was setup with Setup Wizard, and included 64 other files, including
..exe, .dll, .ocx, .stf, .tlb, and many other Windows files.
It has worked fine until XP.
The problem seems that XP can't find system.mdw. XP (and 2000?) stores the
system.mdw file in a different folder than does Windows 98 and previous.
But, the Setup Wizard will not let you change the destination of a system
file in the setup. (I hear that third party setup programs allow this.)
I have updated my Access97-based Asset Management Program to Access 2000 to
better run on 2000 and XP, which expect some .dll files to be in different
folders.
I would now like to package and distribute my program (.mde) as before, but
with Office 2000 Developer.
BUT I can't get there.
When I open the Package and Deploy Wizard from the start menu, it says to
open the P&D Wizard from within the VBA Solutions project. I have only the
Access-based .mde file to begin the setup, and no .exe for the VB6.
Where do I start?
Thanks for the reply,
Bob Sub