Hi, Larry.
perhaps I should have them
purchase Access 2003 and forget about a Runtime version. What do you think of
this approach?
I would make the same decision. There's extra money and effort required on
your part to purchase the VSTO and for building the runtime version of an
application. This will have to be passed on to the customer, so the cost
savings of not purchasing the retail version is quickly overwhelmed by labor
costs if only one license of the software is being sold to the customer.
Many developers put a minimum of 15 to 20 licenses as a break-even point.
Below this and the developer is either going to have to charge a noticeably
higher price per license, or he'll have to "eat it."
You mentioned that you are "starting to get up to speed" in Access 2003. Is
that just this version, or Access in general? Access has a steep learning
curve anyway, and building an application for the runtime version of Access
requires a more robust application (thorough error handling is a _must_) and
the built-in menus and wizards are not available in the runtime, either, so
custom menus and toolbars need to be built. Test out your application with
the /runtime command-line switch to see how the application would look and
act on the user's computer when it's installed with the runtime, and you'll
see what I'm talking about.
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)