Multiple versions of Access w/ Developer

From: Ray Cacciatore (RayCacciatore_at_discussions.microsoft.com)
Date: 01/21/05 

Date: Fri, 21 Jan 2005 07:35:06 -0800

I'm planning to purchase Office 2003 Developer version because I want to
build runtime versions of my Access applications. However, I read somewhere
that when a user already has a previous version of Access and he/she opens
old MDB files, that my runtime versions will get in the way. I.e. their old
MDB files will attempt to run in the runtime environment.

What are the disadvantages of sending a user a complete Access runtime
package?

Thanks in advance

Relevant Pages

  • Re: How to stop library mde being reused
    ... Hmm, yes, I spoted ion a later posting that mdb files are being distributed. ... > that the developer probably took a copy of that to figure out how to ... > I don't think there's any technical solution to this problem. ... > The client should fire the other developer if she won't stop ...
    (comp.databases.ms-access)
  • Question about upgrading
    ... I'm thinking about upgrading my current Office XP Developer Package to the ... with the ability to compile an application in Access into a stand alone ... Office XP Pro to get mdb files and convert them to mde if I did the db in ... So which current package will meet these requirements at this time. ...
    (microsoft.public.access.gettingstarted)