[AccessD] Runtime Vs Full Access Install

Kath ...afaik the runtime is a "package" at install only ...but if a user 
subsequently installs full Access ...any version ...all bets are off because 
your runtime files integrity is dependent upon how the user does the install 
..a "default" install will screw your runtime more often than not because 
it defaults to removing older file versions, even if they are needed by your 
runtime ...Wise/Sage won't block that type of problem from happening either 
but when you reinstall your runtime they will handle the concurrent full 
version issues for you.

..I work with no full Access installs allowed on client systems with the 
exception of developer dedicated workstations ...and no "office" upgrades 
either even if they don't include Access, except by me ...the latter because 
the office vba modules share some common parts with Access vba.

..but I'll be the first to admit that most developers don't have that type 
of control over their app runtime environments and there may well be other, 
better ways to deal with it ...I just find that keeping it clean makes my 
life a lot simpler and my clients with a lot fewer problems.

William

----- Original Message ----- 
From: "Kath Pelletti" <KP at sdsonline.net>
To: <AccessD at databaseadvisors.com>
Sent: Monday, August 01, 2005 9:04 PM
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