Packaging a VB6 Project

I would be *most grateful* if the frequent users of this forum would help me understand WHY my problem is occurring:

Packaging a VB6 Project Using PDW - which has worked fine for me in Win XP up to this point. I am not using Crystal Reports, or using a database etc....so a *detailed explanation* would be greatly appreciated to help me understand the problem.

My basic steps are as follows: Are these OK?
1) Compile project in VB6, then make an EXE.
2) Check that EXE is OK and up to date.
3) Use PDW to package program - generating a setup app to be placed on a laptop using Win XP. Everything is OK.
4) Have to make *changes* to the project. Make new EXE and check all is OK.
5) Remove old Project files from package info. Use PDW to re-package. Check the EXE in the support folder, and all is OK, as Updated.
6) Copy to CD and place on laptop with Win XP. PS: This also works in Win 98
7) Open new program on Laptop only to find out an OLDER version is being used. Why?

I would appreciate a DETAILED comment on process and what might cause this. I was given some info from Randem, however, this did not *seem* to be my problem. I also downloaded a MS doc in his literature on "System Files Are Out of Date", but this does not apply to my situation. Can this that kindly reply also suggest MS papers that are *in line* with what I described. Your help is greatly appreciated.

Also, I would like to know for my files what STEPS in detail and *time* is required to load and use the files Randem has suggested?? I appreciate this, but please understand that a) this PDW has worked fin for me in WIN XP and 98 up to now. b) I generally leave this PDW until my project is ready to go to a client, but I had MANY NEW changes on this project.........

Your detailed comments are GREATLY appreciated.

Thank ALL of you who were able to describe WHY this might happen.
Do you think I should a) move my project to a new file and start again, if so WHY??, b) Should I compile my project with PDW - instead of making an EXE in VB6, if so WHY??


Thank you all very kindly,
Bob334

Why not just create a new PDW project and be done with the issue... You obviously have things in your PDW project pointing to old source. You will either need to open the .pdm file and change the locations of the files, start with a fresh project or leave PDW entirely for there are better options.

Thank you Randem, When you say "Create a NEW PDW Project", what do you mean? Start from scratch, or change the project name? I say this because this project is large in terms of LOC.

So can you explain WHY this may help? Why would the *time* involved to rebuild this be practical, as opposed to some simpler options, I can perform to optimize project completion?

When I open my .pdm [which I have never done], what am I looking for? How can this be obvious to me, if it has not occured before? This is why I would appreciate an explaination..... Thank you kindly.

Starting with a *fresh project* project sounds great and *simplistic*, but what about the project as it is now? It has to be delivered to my client based on timelines, etc.

I understand there are *better* solutions, or options, but this does NOT help me now, with a project that has a deadline.

Randem meant leave your VB project as it is - just create a new installer project in P&DW.

As long as you know which files to add etc, this should only take a couple of minutes.

I don't use PDW (I wonder why ;) ) but open the PDM file (in notepad) and see what you see. That would be the easiest way to answer your question on what it contains.