[AccessD] Seeking your Access Runtime Experiences

John Bartow john at winhaven.net
Tue Mar 1 16:39:15 CST 2005


Mark,
I would include it in the cost to the client and keep ownership of it
yourself. Easy to justify with 1000 units of O2k3 Pro!

Once you write an install script in Wise it is really just a matter of
tweaking it a bit for each app you distribute. No Bell curve, just a high
start up learning period which goes down to almost nothing.

John B. 


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Breen
Sent: Tuesday, March 01, 2005 4:01 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Seeking your Access Runtime Experiences

Hello All you guys that replied to promptly,

firstly, as usual thank you for your detailed comments.

What I am taking from the emails is
1) Runtime is OK to use
2) Be prepared to put a little effort into custom menu's etc.
3) Be prepared to invest installshield or sagekey etc
4) Runtime is common enough.

Just to clarify to you all, the reason I am asking about runtime is that we
have 1000 pc's all with Access 97, but none are licenced for
Acc2003 and we need ADO, not to mention the fact that A97 is no longer the
bleeding edge.

So, I have two choices, continue with A97 and attempt to add ADO and deal
with all the associated difficulties of running an App that is getting a bit
long in the tooth, albeit an nice ol' dear, or convert the entire app to
A2003.

It was this concept that raised the question of runtime, if I propose to the
client that they buy 1000 licences for A2003, they may get a little fright,
but if I propose the relatively small costs of getting set up for Runtime,
then it may not be an issue.

I will keep you all informed as to how it goes, but in the mean time, thank
you very much for your help and comments.

Mark Breen
Happy in Ireland with his ol' pal Access 97.

PS, perhaps next week I will build a web application with Access 2.0 and
Windows 3.1




On Tue, 1 Mar 2005 15:44:28 -0600, John Bartow <john at winhaven.net> wrote:
> IIRC it was InstallShield.
> 
> John B.
> 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of 
> dmcafee at pacbell.net
> Sent: Tuesday, March 01, 2005 3:01 PM
> To: Access Developers discussion and problem solving
> Subject: RE: [AccessD] Seeking your Access Runtime Experiences
> 
> I've been wondering the same thing. Didn't MS go to Wise for help 
> designing the MSI?
> 
> D
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of 
> MartyConnelly
> Sent: Tuesday, March 01, 2005 12:19 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Seeking your Access Runtime Experiences
> 
> Just wondering if anyone has used the .msi file install with SageKey 
> rather than Wise or Install Shield and if there any drawbacks.
> 
> Mark Breen wrote:
> 
> >Hello All,
> >
> >As you may have seen, I am currently enjoying being up to my elbows 
> >in Access 97, a database with 1000 linked oracle tables and hundreds 
> >of forms, reports, queries, pass through queries, dynamically 
> >generated SQL etc and of course loads of code, no errorhandling and 
> >no comments and no documentation!
> >
> >A question arose a few days ago about migrating it to Access 2003 and 
> >using the Runtime version.
> >
> >I have gone online and had a quick read of what is required for 
> >runtime, at its simplest level it seems to be to build a complete 
> >GUI, which I normally do anyway.
> >
> >The only thing that I usually depend on is the filter by form etc 
> >context menu's.
> >
> >Have you guys any comments to make on using the runtime?  Rocky, why 
> >did you not use the Runtime for EZ-MRP?  I am guessing that you 
> >evaluated it and found it troublesome.  Is that the case?
> >
> >In fact, I get the impression that most of us do not use the runtime, 
> >the question I am curious about is why?  It is surely handy to lock 
> >down an app but is it a heavy handed tool?
> >
> >Thanks all for your advice,
> >
> >Mark Breen
> >Ireland
> >
> >
> 
> --
> 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