Doug Murphy
dw-murphy at cox.net
Mon Jun 9 11:37:32 CDT 2008
Hi Robert,
The following is from the file shipped with our Vista compatible scripts.
Note that for Vista installs your app should be in the C:\ProgramData
directory. This is the way our scripts install on Vista and we have not had
any security warning issues.
--------------------------------------
3) Add a new variable COMMON_APP_DATA, and set it to the CommonAppData path.
More information on this is provided in point 4 below. The value can be
determined from reading the registry;
Key =
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell
Folders
Value Name=CommonAppData
Default=%MAINDRIVE%\Documents and Settings\All Users\Start Menu\Programs
4) On Vista, Microsoft formally recommends that all files that are written
to by an application be placed in C:\ProgramData. Therefore, on Vista
MAINDIR should be defaulted to %COMMON_APP_DATA%\%COMPANY%\%PRODUCT% and
%PROGRAM_FILES%\%COMPANY%\%PRODUCT% for all other operating systems. Add
code after the variable OS_VERSION has been initialized (example below).
If OS_VERSION < 6.0 then
Set Variable MAINDIR = %PROGRAM_FILES%\%COMPANY%\%PRODUCT%
Else
Set Variable MAINDIR = %COMMON_APP_DATA%\%COMPANY%\%PRODUCT%
end
---------------------------------------------
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert
Sent: Saturday, June 07, 2008 6:51 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access 2007 SageKey Scripts On Vista Problems
Doug,
So when you install your app. on Vista, the dir is
ProgramData\"Company"\"Product"\ and the SageKey scripts creates these with
Full Control permissions and the "Read Only" option un-ticked?
Are you creating any additional directories (folders) using the scripts? If
so under what part of the script are you tell the script to create them?
It's weird because the scripts are creating dir. structure as it should,
it's just not changing the permissions. I'm just not sure if I'm causing the
script not to do it or if it's a deficiency in the A07 Script.
WBR
~Robert
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy
Sent: Saturday, June 07, 2008 3:12 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Access 2007 SageKey Scripts On Vista Problems
Hello Robert,
I do not have the 2007 scripts but do have the new scripts that do the same
thing when we install our 2002 app on Vista machines. The setup seems to be
working OK on several vista machines. These installations are done by folks
who know nothing more about installing a program than putting the CD in the
drive and following instructions. It took longer than I thought to move my
original Sagekey install over to the new Vista compatible scripts because,
as I recollect, it installs the app on Vista in a different location than on
previous versions of Windows. In our previous scripts I set the directory
location explicitly. The location required for Vista gives all users rights
to run the program, so you have to follow the example script closely when
building yours. I have found that the tech support at Sagekey is great if
you can articulate your issue via email to their tech support site. It may
take a day to get a response, but we have worked through all my issues.
Doug
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert
Sent: Saturday, June 07, 2008 7:12 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Access 2007 SageKey Scripts On Vista Problems
Hello All,
Is there anyone here that is using the A07 SageKey scripts on Vista
successfully?
I have used their A2000 and A2002 scripts with acceptable results, but I'm
having major problems with A2007 scripts.
OS Vista (Updated)
A07 Runtime (latest Version)
SageKey's web site say's:
"Installations built using our tools will automatically be able to run
macros without displaying any security warnings. You will also be able to
add additional folders as trusted locations with our tools"
In the scripts they also say:
"At the end of the install, the Sagekey scripts will open up permissions on
MAINDIR to give all Users Full Control. This is done to ensure that
regardless of where the end user chooses to install the application, it will
run properly."
But it appears that this is not happening. This is what is happening:
1) Installation processes correctly (As Administrator)
2) User logs in to my Application (.mde) and is confronted by a security
warning.
3) If the user selects continue, the user is then confronted by my
re-linking code. The problem is, it *appears* that the folder(s) created by
the SageKey scripts are {Read Only}, and the permissions for the folder are
not set to full control.
4) This causes the re-linking code to fail, and my shuts down.
If I modify my root directory (located under the ProgramData dir) G.B.S.
(un-tick Read Only) and set permissions to full control all (with the
exception of the security msg) loads fine.
Steve, from SageKey, has address some small minor issues, but interestingly
enough not these, which are in my view major problems.
Any Idea's ???
WBR
~Robert
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com