UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> Package Solution: Additional registry keys type    
 
   
SilentFiddler
post May 6 2009, 07:12 AM
Post#1



Posts: 5
Joined: 17-July 06
From: Leicester, England


I am trying to distribute a runtime application in which I need to have a registry key set:
[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Access\Security\Trusted Locations] "AllowNetworkLocations"=dword:00000001
The details for the Package Solution wizard on:
http://msdn.microsoft.com/en-us/library/bb501030.asp
show that you can add registry keys and set name, type, value etc, but my version of the Developer Extensions does not include Type on Page 3 of the Wizard.
I have downloaded the January 09 release of the DE and re-installed, but still no luck.
Has anybody had any success in getting registry keys set through the installation.
I have been successful with the following:
1. Manually setting the registry key.
2. Creating a registry settings file, and running that to set the registry keys.
3. Setting up a key for the path to a trusted location within the Package Solutions Wizard.
The thing I have the problem with is setting the AllowNetworkSettings key, because this needs to be type DWORD and my developer extensions doesn't have anywhere (that I can find!) to choose the type.
I could "crunch" a solution by using 1 or 2 above (probably 2) but as this is a distributed solution, I want to be able to just give users an install package with nothing else to do afterwards.
Any help would be appreciated.
Thanks
Lee
Go to the top of the page
 
AlbertKallal
post May 6 2009, 09:21 AM
Post#2


UtterAccess VIP
Posts: 2,534
Joined: 12-April 07
From: Edmonton, Alberta Canada


You dont actualy "set" the type, it based on how you enter the data:
g:
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
Note how the "#" before the number represnets REG_DWORD
The data types are outlined here:
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)
Albert D. Kallal
Edmonton, Alberta Canada
kallal@msn.com
Go to the top of the page
 
SilentFiddler
post May 6 2009, 09:38 AM
Post#3



Posts: 5
Joined: 17-July 06
From: Leicester, England


Thanks - you are a genius!!

You have no idea how I've been going round in circles to try and sort this out.
That's great - it works - thanks.

Lee
Edited by: SilentFiddler on Wed May 6 11:09:34 EDT 2009.
Go to the top of the page
 


Custom Search
RSSSearch   Top   Lo-Fi    18th October 2017 - 10:23 PM