[AccessD] Sage Key Purchase

Doug Murphy dw-murphy at cox.net
Fri Feb 4 15:07:09 CST 2005


John,

I don't want to give the impression that I had any significant trouble with
the Wise/Sagekey approach.  Just the opposite, I had problems with the
Access 97 Package and Deployment wizard that came with 97 Developer.  That
is the reason I invested in Wise/Sagekey and upgraded to Office 2002.

I have run into a minor glitch or two with the present approach but the
folks at Sagekey have always been quick to respond to my questions and right
on the problem when it was something in their script.

Doug

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bartow
Sent: Friday, February 04, 2005 12:55 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Sage Key Purchase


Ah, there's always a bad story lurking around the corner, waiting to join
one's repetoire. Sorry to hear of your bad experience.

I use the Sagekey scripts as a starting point. I also do a lot of Wise
script editing. No problems here (yet) knock on wood - or for you Brits -
touch wood.

John "I used the Wise wizards once for a joke program, worked great!" B.
 


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy
Sent: Friday, February 04, 2005 1:34 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Sage Key Purchase

I have been lurking on this discussion, but need to endorse this testing
approach.  I use Wise with Access 2002 and Sagekey scripts.  I have test
environments for clean machines and machines with various versions of Office
and Windows.  I have found some problems in testing our installations before
going public.  One involved an interaction with the Sagekey scripts, which
they imediately fixed as soon as we localized the cause.  So far we have not
had any problems with our customers installations.  Getting the whole
package is expensive and testing is time consuming, but it is a lot easier
than being on the phone full time with a bunch of irate customers.

I just saw an article the other day on developing installation packages and
one recommendation that I thought wise was to have a clean machine to build
the installation packages.  In this case a clean machine would be one with
only OfficeXP Developer, in our case, Wise and the Sagekey scripts. Office
should have all the latest service packs.  Theoreticly if you use the set of
install files Sagekey makes available with their scripts you shouldn't have
to worry about DLL hell, but Murphy's law says different.  I learned this
lesson in building an installation with Access 97 Developer on a machine
that also had Access 2000 on it.  The MS packaging program pulled some 2000
files into the installation.  I was testing on our lap top and after
installing and trying to run the installation hosed the machine.  I had to
completely reformat the drive to fix it. 

With the test drive approach you can just have one set up with the proper
clean versions of Windows, Office and the installation programs.  I don't do
this often, but when required I'd just install the Ghosted setup and build
the installation.

Doug


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bartow
Sent: Friday, February 04, 2005 9:42 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Sage Key Purchase


Marty,
Don't know about that but Sagekey actually has very "sage" advice on setting
up a system for testing purposes.

Have an extra hard drive and Ghost (or whatever your imaging product is) an
image to that hard of all the various configurations you may need to test
for. For instance.

Install XP and ghost it.
Install Office 97 and ghost it.
Install Office 2k and ghost it.
Replace current image with the first and install Office 2k (without the 97
being there first) Ghost it. ... Install SP2 and Ghost it.

Eventually you have a clean Ghost Image of all these configurations. In one
day you can test against dozens of possibilities by retrieving a Ghost image
installing and testing the software and when satisfied retrieving the next
ghost  configuration. It does work well. I would add the recommendation of
having a separate computer to do this with besides the one your using for
daily tasks.


John B. 

 


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly
Sent: Friday, February 04, 2005 11:11 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Sage Key Purchase

Rather than install different OS on each machine, you might try VMWare to
put each OS as a seperate boot on one machine, I don't know what this does
to image backups though.

Nicholson, Karen wrote:

>This database is being distributed worldwide, from Hong Kong to
>England. I am running into the Windows XP environment not wanting to 
>run an Access 2000 Runtime.  Got the Access 2003 runtime working, but 
>now I don't know if it will run on Windows XP.  If it runs on Windows 
>XP, will it run on Windows 2000?  I used to have a bunch of computers 
>at home with various operating systems, now I have none that work.  The 
>others walked away.  Funny how that happens.  Not to fear, to Sam's 
>Club I go to get a new PC tonight. I can't take it anymore!
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William
>Hindman
>Sent: Thursday, February 03, 2005 11:48 PM
>To: Access Developers discussion and problem solving
>Subject: Re: [AccessD] Sage Key Purchase
>
>
>..consider it done :)
>
>..but really, have you ever seen one?
>
>William Hindman
>
>
>----- Original Message -----
>From: "John Bartow" <john at winhaven.net>
>To: "'Access Developers discussion and problem solving'" 
><accessd at databaseadvisors.com>
>Sent: Thursday, February 03, 2005 10:47 PM
>Subject: RE: [AccessD] Sage Key Purchase
>
>
>  
>
>>Qualify that statement with a "consistent" corporate environment.
>>
>>JMTC
>>
>>John B.
>>
>>
>>
>>
>>-----Original Message-----
>>From: accessd-bounces at databaseadvisors.com
>>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William
>>    
>>
>Hindman
>  
>
>>Sent: Thursday, February 03, 2005 9:07 PM
>>To: Access Developers discussion and problem solving
>>Subject: Re: [AccessD] Sage Key Purchase
>>
>>..if you are running Access strictly within the corporate environment,
>>    
>>
>
>  
>
>>there
>>may be no good reason to use anything other than the packager included
>>    
>>
>in
>  
>
>>the VST ...Wise/SageKey earn their money when you are installing
>>    
>>
>Access in
>  
>
>>unknown/uncontrolled environments ...but within a corporate
>>    
>>
>environment,
>  
>
>>VST
>>is more than adequate ime.
>>
>>William Hindman
>>
>>
>>----- Original Message -----
>>From: "Charlotte Foust" <cfoust at infostatsystems.com>
>>To: "Access Developers discussion and problem solving"
>><accessd at databaseadvisors.com>
>>Sent: Thursday, February 03, 2005 11:31 AM
>>Subject: RE: [AccessD] Sage Key Purchase
>>
>>
>>    
>>
>>>You need scripts to match the version of the runtime you're
>>>distributing.
>>>
>>>Charlotte Foust
>>>
>>>
>>>-----Original Message-----
>>>From: Nicholson, Karen [mailto:cyx5 at cdc.gov]
>>>Sent: Thursday, February 03, 2005 4:48 AM
>>>To: accessd at databaseadvisors.com
>>>Subject: [AccessD] Sage Key Purchase
>>>
>>>
>>>What is the best version of SageKey to buy to make executables for
>>>Access databases?  Right now we are using Access XP, but the
>>>      
>>>
>corporation
>  
>
>>>MAY be going to Access 2003, they are not sure.  Would we have to buy
>>>two products for that?  Advice needed, Thanks!!!  Glad to be back
>>>      
>>>
>after
>  
>
>>>a day off...
>>>--
>>>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
>>
>>--
>>AccessD mailing list
>>AccessD at databaseadvisors.com 
>>http://databaseadvisors.com/mailman/listinfo/accessd
>>Website: http://www.databaseadvisors.com
>>
>>    
>>

--
Marty Connelly
Victoria, B.C.
Canada



--
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

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com





More information about the AccessD mailing list