Access 2003 Developer Extensions - Package Wizard

  • Thread starter Thread starter Guest
  • Start date Start date
I am not sure what you mean that it always packages a new install?

To update your software, you run a split database? Correct?

The standard approach here is to simply make a new install, and DO NOT
INCLUDE the runtime here. The old mde file with your code will simply be
overwritten when you do this.

You are not `100% clear on what you mean by "update". However, if you have
not split your data, and code/forms etc. into two parts, then how would you
update just a few new forms? (answer: you can't!!...).

Remember, the runtime system is the same as normal ms-access,a nd is not
special in terms of what it can, and cannot do.

I guess the question here is how do / did you update users who are NOT using
the runtime?
 
Albert D. Kallal said:
I am not sure what you mean that it always packages a new install?

To update your software, you run a split database? Correct?

The standard approach here is to simply make a new install, and DO NOT
INCLUDE the runtime here. The old mde file with your code will simply be
overwritten when you do this.

You are not `100% clear on what you mean by "update". However, if you have
not split your data, and code/forms etc. into two parts, then how would you
update just a few new forms? (answer: you can't!!...).

Remember, the runtime system is the same as normal ms-access,a nd is not
special in terms of what it can, and cannot do.

I guess the question here is how do / did you update users who are NOT using
the runtime?


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(e-mail address removed)
http://www.members.shaw.ca/AlbertKallal
Click to expand...
 
Albert,
I'm new at this. I have split my database and built a new install with a
different version and did not include runtime, however, when I install on the
target machine with a previous version I get the error message "Another
version of this product is already installed. Installation of this version
cannot continue."
What Im I doing wrong?

Bitsy
 
Bitsy said:
Albert,
I'm new at this. I have split my database and built a new install with a
different version and did not include runtime, however, when I install on
the
target machine with a previous version I get the error message "Another
version of this product is already installed. Installation of this
version
cannot continue."
What Im I doing wrong?
Click to expand...

Ok...good stuff here! I just wanted to be sure you understood that the
"wizard" does not have the ability to update individual forms and reports.

The package system can only deploy a whole new file..and not parts
of the file. You now have made it 100% clear you understand this process.
(I was just trying be sure of this...not hard on you!!...sorry!!).

Ok, what happens here is that you used the "same" template for the original
install as the 2nd update. The installer does generate those "long" product
keys. So, on page (step 5 of 7) of the installer, simply cursor into the
Product code field, and erase the big long number. (just hit the space bar,
or back space key
to erase the value. When you hit tab, a "new" key generated. Do the same for
the Upgrade
code.

Now, when you install..you will NOT get a message to the product already
being installed.

Another solution here is to simply create a NEW blank template (do NOT copy
the old package template), and again you will be able to install the
updates...
 
Albert,
Thanks much, that worked. However, the 2nd update did not overwrite the
original version, so end result is I have two copies, the original and the
2nd update versions. Is there anyway to overwrite the original with the
update?
 
Back
Top