Need help on creating registry keys

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Where do I find help with creating registry keys using the ADE Packaging
Wizard 2003?

What is the default root? What do I enter in the "key" field? I can use VBA
coding to create and read registry entries but this part of the packager is
incomprehensible. I have spent two hours searching the web for some kind if
help.
 
OK Thanks Albert - you showed me the format of what I need to enter and it
works fine. Now can you tell me how to indicate which file are optionally
installed when the user requests a "custom" install?
 
When using the package wizard, on the step 4 of 7, you are given a screen in
which you can make registry entries.

Fro example, on that page, I include the following registry enters to get
rid of ALL nag and security prompts
(I do this by setting macro security to low).

So, on that page, the keys are:

Root: Local Machine
Key: Software\Microsoft\Office\11.0\Access\Security
Name: level
Value #00000001

and the jet sandbox mode set to work with access

Root: Local Machine
Key: SOFTWARE\Microsoft\Jet\4.0\Engines
Name: SandBoxMode
Value #00000002

So, just enter the keys on the step "4" of 7 page. It is laid out as a
sub-form..and you can enter as many keys as you want...
 
Bill said:
OK Thanks Albert - you showed me the format of what I need to enter and it
works fine. Now can you tell me how to indicate which file are optionally
installed when the user requests a "custom" install?

"Albert D. Kallal" wrote:
Click to expand...

I never used that feature.

In fact, I actually only use the package wizard to build the runtime. You
should as a habit separate you install into 3 parts:


1) - the runtime install. Once you client has this installed, there is NO
need to have a huge 34 meg runtime sitting around in your additional
installing and updates. Further, if the customer already has access 2003,
then you just saved 34 megs of space/install time.

2) If you separate the runtime and your apcpation, then when you go to
un-install your apcpation you will not be prompted for the original install
disk you made (if you check here...you see a good number of people asking
how to un-install a package, but their client/customer has lost the disk you
made....and you don't have the original install saved. if you package your
application + runtime..then for a user to un-install..they will be prompted
for that disk. If you separate them...then they are not.

3) you data part. You are running a split database..right? (else, you better
explain to me how you going to offer updates).

Since step #1, and #3 are a RARE occurrence...especially after you installed
your appcation, then really, you only goal is step #2..since that what you
do for updates, and for users that don't need to install the data part (such
as on a network).

In fact, for ease of use, and the fact that I am *just* installing a
shortcut on the desktop, and a mde file...I don't use the package wizard for
that anymore. (I use the free inno installer).

Since the inno produces a single .exe file, then updates are easy. Here is a
set of screen shots as to how a customer updates my software:

http://www.kallal.ca/ridestutorialp/upgrade.html

the package wizard is really very weak, and I would ONLY use it to install
the runtime. For everything else...I use the free inno installer...

http://www.jrsoftware.org/isinfo.php
 
Good advice. (And yes I have a back end file which I was doing to install in
a separate package.)

Is there somewhere with some sample scripts to that I get get a fast start
with the Inno installer?
 
Back
Top