Access 2007 Package Deployment Question

[tkosel]

I am using the Access 2007 Developer Package Deployment feature to deploy a
package using runtime. It seems to work, but two things are wrong.

1. I am uing the package Deployment feature to add a registry key. I wand
to add "HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\Security" as
a key. The name is "DisableHyperlinkWarning," and I want it to be a DWORD
value of 1. I can get it all to work right except for the Dword part. It
creates it as a REG_SZ Type. Does anyone know how I can specify that it be a
DWORD value?

2. All the stuff installs right using the Install Package. (Run Time, DB,
etc.) When I run it, it starts to run, I see the 2007 like interface, but
then it stops and says "Unrecognizable Database Format".

Any ideas on either fo these?

 

[Albert D. Kallal]

I am using the Access 2007 Developer Package Deployment feature to deploy a
package using runtime. It seems to work, but two things are wrong.

1. I am uing the package Deployment feature to add a registry key. I wand
to add "HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\Security"
as
a key. The name is "DisableHyperlinkWarning," and I want it to be a DWORD
value of 1. I can get it all to work right except for the Dword part. It
creates it as a REG_SZ Type. Does anyone know how I can specify that it
be a
DWORD value?

Reg data types:
http://msdn2.microsoft.com/en-us/library/aa371168.aspx

we see:
Prefix #x
The value is interpreted and stored as a hexadecimal value
(REG_BINARY).

Prefix #%
The value is interpreted and stored as an expandable string
(REG_EXPAND_SZ).

Prefix #
The value is interpreted and stored as an integer (REG_DWORD).

So, use:

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

ROOT:Local Machine
Key: Software\Microsoft\Office\11.0\Access\Security
Name:Level
Value:#00000001

Above examples are for office 2003, and it would set macro secirty to low,
and thus disable secirty prompts.

I don't have a equal set for 2007 handy.

2. All the stuff installs right using the Install Package. (Run Time,
DB,
etc.) When I run it, it starts to run, I see the 2007 like interface, but
then it stops and says "Unrecognizable Database Format".

Hum. I try simply copying any old access database you have to that machine,
and see if it runs.

Keep in mind that there's no special connection between your database that
you deployed, and the installation of the runtime. Once you have the
database installed on the target machine, you can simply double click on any
database that you copy to that machine, and it will launch as normal. The
runtime is simply a full version of MS access with some of the design tools
removed, but for the most part it's behaviors much the same as when you
install the full version.

You don't have to use the package wizard to actually deploy and installed
your software, **once** you have the runtime installed. Thus, you can simply
copy the file to that computer, and then double click on mdb, or accDB file
to launch it (the same as if you had the full version of MS access
installed).

So, now that you have the runtime installed that machine, try copying a few
test files to that machine and click on and see if they run. as I mentioned,
there's no special connection between the runtime being installed, and your
databases that you copy to that target machine.

 

[tkosel]

Mr. Kallal,

Thanks for your assistance. You suggestion on the registry change worked
great.

As far as the unrecognizable format issue, I think I discovered that you
cannot package an ".accde" file for use with the runtime? I created a
package using the ".accdb" file and it worked fine. The installed DB was
".accdr" which I assume is runtime. Is this ".accdr" format as secure as an
".accde" format?

Now I have only one issue outstanding. When the application runs, I get a
Security Notice. "A potential security concern has been identified . . ."
It goes on to explain that I should only run it if I trust the source.
However, I cannot say that I want to always trust it. Every time I run it I
get the same message. I am sure there is a way to eliminate it, but cannot
find it explained clearly anywhere! Any ideas?

Again, thanks for your assistance with the Registry!!!!