Include .mde in Package?

[Bill Sturdevant]

This is undoubtedly a stupid question and the answer is right in front og my
eyes. but is it possible to incorporate a .mde version of the Access 2002
application into the package instead of including the .mdb?

If so, how?

Also, once I create a package, I thought I would have to just go in and add
a newer version of the application. Instead it seems I am contantly creating
new packages. Being self-trained, I am not sophisticated enough yet to be
using Visual Source Safe or anything like it. Nor, for that matter, do I
seem to have time to stop and "do the right thing". To make a new version of
my application I just copy and rename slightly to include the version number
in the name.

Where can I find an in-depth discussion of this whole issue?

 

[Chris Mills]

This is undoubtedly a stupid question and the answer is right in front og my

eyes. but is it possible to incorporate a .mde version of the Access 2002
application into the package instead of including the .mdb?

Yes you can. I don't have the Access 2002 PDW up right now, but can't you
include the mde in the list and untick the mdb (you may not be able to remove
mdb from the list but you can untick it).

If necessary, you can modify the Setup.LST after package generation.

Also, once I create a package, I thought I would have to just go in and add
a newer version of the application. Instead it seems I am contantly creating
new packages. Being self-trained, I am not sophisticated enough yet to be
using Visual Source Safe or anything like it. Nor, for that matter, do I
seem to have time to stop and "do the right thing". To make a new version of
my application I just copy and rename slightly to include the version number
in the name.

That's one of the big limitations of the Access PDW. And once you
install-more-than-once you may have quite a job removing everything. I guess
it's one of the many reasons why "most" developers use other "professional"
installation packages.

For the reason you mention, I provide upgrades on CD by adding an "Upgrade"
folder, which just has the mdb. Just copying a file may upset some end-users,
but it's the simplest way I can think of.

Where can I find an in-depth discussion of this whole issue?

Dunno. Setupconfig, devtoolkits, developers.toolkitode sounds like a good
place. Microsoft do not advertise the limitations of PDW so far as I know.

www.sagekey.com - that might have articles which help.

Chris

 

[Chris Mills]

Actually, I think you can incorporate an mde directly, by opening the mde and
hitting ALT F11. You can get to the code window this way (even though there's
no code) and still run PDW from there.

Chris

 

[Paul Overway]

Ctrl-G works too...provided he hasn't disabled special keys yet. The way
I've done this in the past is to create the MDE...without disabling any
special keys. Open the MDE using shift key, press Ctrl-G, run the packaging
wizard...then I replaced the MDE in the Support folder with the one I
actually wanted to distribute (i.e., with AllowBypassKey false, and special
keys disabled).