[AccessD] Seeking your Access Runtime Experiences

Hi Mark,
If you know all of the machines your app will be running on have the same
configuration and includes Access there would be little point to use
runtime.

I use a runtime via Wise Install Builder and Sagekey Access scripts for
everything I distribute. Saves the client money, ensures you have what you
need on the end user's machine and has generally saved me a lot of headaches
over the last half dozen years. You do have to do a little prep for it for
which the "/runtime" command line switch comes in handy. Making your own
toolbars and menus is probably the biggest issue.

I can offer no advice on native MS runtime building capability lately. All I
can say it that it used to be poor.

The issue that seems to pop up with most people is the cost of Wise/Sagekey.
I have seen it as a cost savings but then I also can justify it because I'm
the boss and would rather have money coming in than complaints :o)

I can relay to you that one of my (very fiscally short-sighted) clients that
I do general consulting for has an Access application that is not
distributed via runtime. It has cost them more in the last year to purchase
Office Pro than it would have cost to just buy the developer Wise/Sagekey
and send them to training to learn how to use it. They have no reason to
purchase Office Pro other than this app and it is over double the cost to
have Office 2k3 Pro versus Office k3 Basic.)

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 11:09 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Seeking your Access Runtime Experiences

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
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com