Comments

# Andre Minhorst said on April 9, 2008 4:11 AM:

Hi Clint,

sorry, but the German runtime writes nothing to

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\Trusted Locations

So security prompts still appear.

Moreover I wonder how AccessRuntime.exe should know where the user will install his .accdb file? Or does he have to install all applications to the folder containing msaccess.exe?

# Carlo Costarella said on April 9, 2008 5:09 AM:

In the Italian runtime writes nothing to

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\Trusted Locations

So security prompts still appear...

# Sascha Trowitzsch said on April 9, 2008 6:50 AM:

Hi Clint,

Could you please clear up wha you ment exactly?

- I installed the german runtime. A look into the registry: No keys under access\security\trusted locations.

- Startet an accdb: Security warning.

- Added a trusted location for the folder containing the accdb with a tool that writes an entry to the registry.

- Opened the accdb again: Security warning.

I tried anything but the warnings *always* rise up!

Sascha

# Edwin Blancovitch said on April 9, 2008 11:58 AM:

Hey guys, i use inno set up t deploy my apps, and i just created some lines to add my folder to the trsuted folders section in the registry.

so thats all, from the start even without sp1, i have no security warnings.

if you need my lines to add to your inno setup section, ask me and i will post the here.

By the way inno setup is free.

# Garry said on April 9, 2008 12:12 PM:

Hey Edwin,

I use inno and would very much appreciate seeing your code.

Do you digitally sign your Access apps and which Access version do you deploy them in?

Thanks,

Garry

# J. B. Tome Jr said on April 9, 2008 3:50 PM:

hi, Edwin Blancovitch,

May I have yours Inno Setup Scripts? As far as I know, other application could write the same number in the "HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\Trusted Locations". How do you prevent that?

Thanks in advance

# M T Johnson said on April 9, 2008 11:42 PM:

How about allowing an end-user of an  app to allow update queries without 3-5 'safety warnings'?

Thanks,

M

# muffin gun said on April 10, 2008 1:05 AM:

Does anyone know if the access 2007 runtime screws up installations of retail versions of Access (any ver)? No prev Access runtime would co-exist with retail Access unless used in conjunction with a script like sagekey etc. I'd be surprised if the Access team did any better with 2007 but thought I'd ask.

# Sascha Trowitzsch said on April 10, 2008 5:03 AM:

@Edwin, "so thats all, from the start even without sp1, i have no security warnings."

1st: we where talking about the localized verson of the runtime. Maybe there'a difference in behaviour to the english one.

2nd: The security warnings come up *only* with the new version and *not* with the former Sp1-less one - *despite* the written registry keys.

There are several people in german ngs that could confirm this behaviour.

# Vladimir Cvajniga said on April 12, 2008 3:09 AM:

muffin gun: This is why I keep asking for a professional PDW tool for Access. Co-existence with other versions of Access on the same machine is a neverending story...

# Vladimir Cvajniga said on April 12, 2008 3:11 AM:

Edwin Blancovitch: A colleague of mine has tried several ways to implement your Ribbon thoughts... until his A2007 totally collapsed!!! He thinks he will have to re-install Office 2007... :-(

# Edwin Blancovitch said on April 13, 2008 6:44 PM:

Ok guys; here is my story.

First of all sorry, I was disconnected some days due to a lot of work.

Garry:

For those who need to know how do I deploy, I use access 2007 now, in the past I was using access 2003, and initially in 2003 I was using digital signatures, but they only last 1 year, so I discovered a way using sandbox (documented in knowledge base) how to get rid of that.

When 2007 came to the market, I waited for the runtime, cannot live without it .

So now I do not use digital signatures, I just use trusted folders, isn’t that great 

J. B. Tome :

When I deploy I just deploy my app, I deploy the runtime via ftp, in a separate installation

And I use inno setup to deploy m apps, when using inno setup I just add these lines of code, to the registry section.

=============================

[Registry]

; the access security warning override.

; for this to work the windows service pack 2 must be installed.

Root: HKLM; SubKey: Software\Microsoft\Jet\4.0\Engines; ValueType: dword; ValueName: SandBoxMode; ValueData: 00000002

Root: HKLM; SubKey: Software\Microsoft\Office\12.0\Access\Security; ValueType: dword; Valuename: Level; ValueData: 00000001

Root: HKCU; SubKey: Software\Microsoft\Office\12.0\Access\Security; ValueType: dword; Valuename: VBAWarnings; Valuedata:00000001

Root: HKCU; SubKey: Software\Microsoft\Office\12.0\Access\Security\Trusted Locations\Location(5); ValueType: string; Valuename: Path; Valuedata:{app}

Root: HKCU; SubKey: Software\Microsoft\Office\12.0\Access\Security\Trusted Locations\Location(5); ValueType: dword; Valuename: AllowSubfolders; Valuedata:00000001

Root: HKCU; SubKey: Software\Microsoft\Office\12.0\Access\Security\Trusted Locations\Location(5); ValueType: string; Valuename: "Description"; Valuedata:Easy Payroll Folder

=============================

For those who ask, Yes, other app can override my values, but what can I do, just reinstall them, or create  a different number, see the location(5) well you can have your own number.

M T Johnson: I think you need to set a value in your db property(s) confirm update queries, set them to no, and you will get rid of those 

Sascha Trowitzsch, I just use English and Spanish version of the runtime, but so far I have no problems with my security warnings , look at the code I submitted here using inno setup, uou can also use other apps to deploy your app, but inno is very flexible and easy to use, and is free, what else can you ask.

Vladimir Cvajniga, I have deployed more than 100 units of my app to different scenarios, windows xp, windows vista, and in different environments, like domain, or workgroups, even stand alone, and all of them are working ok.

But you know what, is because I have no played with my registry, I just installed on a clean pc, you can do that and play with virtual pc, try in a clean installed version of office 2007.

At first I have some problems using access 2003 and access 2007 in the same pc, I just use a new clean install of office 2007 and all problems were solved, so in my clients I instructed them to remove the 2003 runtime only, and install the new 2007 runtime, some of them the majority still have office 2003, and is working ok.

But regarding my apps, most of them have the runtime, I can recall some of them having access 2003 because they have the professional version of office 2003.

But Vladimir Cvajniga, all i have asked to you is to select a cmmand bar from the interface, so why it will have to reinstall office, i think there must be something else in the environment, dont you think?

If you need me, i can hel you more, you seem to be a very serious developer, ask me and i will send you my email or phone number if you need me more.

# Sascha Trowitzsch said on April 14, 2008 11:30 AM:

Edwin, I mentioned: "despite the written reg keys"!

Sorry, I'm no newbie and know how to write registry keys, how to build install packages, ...

Your remarks imply that we would't know how to set trusted locations - but that's not the point.

The behaviour of the german ARTSP1 looks more like a bug.

# Edwin Blancovitch said on April 14, 2008 4:27 PM:

Sascha Trowitzsch : sorry to hear that, i use the english and spanish version of the runtime, i have never used any other.

If i can be of any help, dont hesitate to ask me, and i will do  my best t help you.

Edwin Blancovitch

# muffin gun said on April 14, 2008 6:44 PM:

Thanks Vladimir Cvajniga for responding, I take it that means that once again the MS Access team has not taken their own project seriously, and that installing the Access 2007 runtime fouls up other installations of Access.

Gee how about we hear from the MS Access dev team on this topic? How can you take yourselves seriously? I mean, you take some time to build an Access runtime, and then for over a decade don't care that it torpedoes any preexisting Access deployment, or the other way around? It's unfathomable and unprofessional, makes Access into a one of a kind badly behaved development tool. Now into the second decade of this?

New Comments to this post are disabled