[AccessD] Runtime Vs Full Access Install

William - maybe I have misunderstood. I thought that by including all dll's (or other files referred to in the vba references)  in the runtime install package, that it could then be standalone. By that I mean that it would run regardless of whether the user had (any version of Access) or not, as it is a packaged entity. 

Have I got that wrong? (And I am assuming using Sage / Wise)

Kath


----- Original Message ----- 
  From: William Hindman 
  To: Access Developers discussion and problem solving 
  Sent: Thursday, July 28, 2005 3:26 PM
  Subject: Re: [AccessD] Runtime Vs Full Access Install


  ..hhhmmm ...either I'm misreading you or there is a fundamental 
  misunderstanding somewhere in here ...a runtime mdb/mde is exactly the same 
  as a full install mdb/mde ...the difference is that Access itself is not 
  fully installed in a runtime ...the design/coding elements are not there so 
  a user can't change anything ...it runs exactly as you designed it to run.

  ..if you have an A97 mdb and an A2k runtime it should still run as long as 
  the references are there ...but the reverse is not true ...so I use startup 
  code to check the installed version and call the corresponding fe mdb/mde.

  ..if you invest in the wise install tools, they handle those issues much 
  better than the native Access distribution tools do and the default is to 
  let them do all the work for you.

  William