Application Deployment

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I need to deploy an Access application (.mdb) to multiple users that don't have Access. I've heard that if I buy the one of the SDKs, I can deploy my applications with the runtime library from the SDK. Question... Which SDK should I buy?
 
My personal opinion:

Deploying the Access "runtime only" version is so problematic, that WHOLE
3rd part industries have grown up to sell supporting tools. So the developer
pays $x00 for the Access runtime version, then >another< $x00 to SageKey
(for example) for extra scripts, to make it all work!

Save yourself a lot of grief. >If feasible<, say to your customers: "This
application requires a working copy of Microsoft Access version ... on your
PC".

HTH,
TC


GregCarlson said:
I need to deploy an Access application (.mdb) to multiple users that don't
Click to expand...
have Access. I've heard that if I buy the one of the SDKs, I can deploy my
applications with the runtime library from the SDK. Question... Which SDK
should I buy?
 
I actually agree with you.

However, if you do purchase the sagekey stuff, it is all workable, and at
least as good as a VB install you build.

Considering what development tools cost these days...the over layout for
Sagekey, and Wise or InstallSheild , and the offfice Developer edition is
not much cost. So, for the cost of less then 1 week of developer time, you
get a working solution. This sounds like a bargain to me.
 
Back
Top