[AccessD] Runtime Vs Full Access Install

Charlotte Foust cfoust at infostatsystems.com
Tue Aug 2 10:40:23 CDT 2005


Any confusion is probably in mixing issues of MDE/MDB and runtime.  The
two have nothing to do with each other.  The runtime includes the dlls
and licenses required to run an Access database without any particular
version of Access installed.  An MDE is a form of MDB that no longer
contains any code and does not allow some operations, regardless of
whether it is run using a runtime for full installed Access.  Does that
clear up the confusion?

Charlotte Foust


-----Original Message-----
From: Kath Pelletti [mailto:KP at sdsonline.net] 
Sent: Monday, August 01, 2005 6:05 PM
To: AccessD at databaseadvisors.com
Subject: Re: [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

-- 
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