Re: Multiple versions with VB5
- From: "MikeD" <nobody@xxxxxxxxxxx>
- Date: Thu, 19 Jun 2008 14:20:14 -0400
"Henning" <computer_hero@xxxxxxxxxxxx> wrote in message news:485a6323$0$12246$57c3e1d3@xxxxxxxxxxxxxxxxxxx
"Dave O." <nobody@xxxxxxxxxxx> skrev i meddelandet news:eY7aMze0IHA.3968@xxxxxxxxxxxxxxxxxxxxxxx
"Jan Hyde (VB MVP)" <StellaDrinker@xxxxxxxxxxxxxxxxxxx> wrote in message news:3l4k541kp6bnh0grokcmas6bcrmq8i0l1m@xxxxxxxxxx
"tadamsmar@xxxxxxxxx" <tadamsmar@xxxxxxxxx>'s wild thoughts
I think it might help if you explain why you need multiple
versions.
--
Jan Hyde
Indeed, you might find it easier to maintain a single application but use command line parameters or a configuration file to
enable the different functionality required.
Maintaining a selection of marginally different versions is fraught with danger and given time you will screw up, not "might" or
"could" but "will" - sorry.
Dave O.
If you want different versions, and will update them individually then. Start some new projects, one for each version. Assuming
the version you have now is the base for them all, copy all forms, .bas and so on to each new project directory. Chose project add
existing modules to get separate copies of current project in each new project.
Personally, I think what I do is just maintain a single project and use conditional compilation to create different "versions".
--
Mike
Microsoft Visual Basic MVP
.
- Follow-Ups:
- Re: Multiple versions with VB5
- From: Henning
- Re: Multiple versions with VB5
- References:
- Multiple versions with VB5
- From: tadamsmar@xxxxxxxxx
- Re: Multiple versions with VB5
- From: Jan Hyde (VB MVP)
- Re: Multiple versions with VB5
- From: Dave O.
- Re: Multiple versions with VB5
- From: Henning
- Multiple versions with VB5
- Prev by Date: Re: how can I match one code with many other codes?
- Next by Date: Re: Opening Txt Files
- Previous by thread: Re: Multiple versions with VB5
- Next by thread: Re: Multiple versions with VB5
- Index(es):
Relevant Pages
|