I must have been thinking of a different setup program, probably the one
from the developer kit for MS Office. You could modify the setup1.exe
program itself, since the source code is part of the VB install, but
that is a bit more elaborate.
Why not just put the update code in the program itself? You can probably
write something to detect the old database, and offer to upgrade to the
new format, or do it silently when the program starts up. Users are used
to seeing this sort of thing these days, I doubt they will mind.
"Thomas" <thomas.vangeel RemoveThis @belgacom.net> wrote in message
news:1a35b56f.0502211222.da6cfae@posting.google.com...
| Thanks Steve,
|
| I also thought of that solution, but where do I specify in the setup
| to run that separate program? And could I instantly remove it again,
| so that the customer doesn't notice it?
|
| Thomas.
|
| "Steve Gerrard" <mynamehere RemoveThis @comcast.net> wrote in message
news:<-O6dnSH4id2rIInfRVn-1A RemoveThis @comcast.com>...
| >
| > I don't think there is a way to do that directly in the setup. I
think
| > you can get the setup to run a separate small VB program, though.
| >
| > Whether it is a separate program run from the setup, or a command in
the
| > main program, the simplest way I have found to change the database
| > structure is to run a VB procedure that creates a new empty database
in
| > the new format, then copies the data from the old database into the
new
| > one. The exact sequence needed depends on the structure of your
data.
| > The other choice is to use a VB procedure to add the new field
| > definition to the existing database. >> Stay informed about: Package & Deployment wizard: Update a database