Access 2002 Runtime "problem"

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

Guest

Hi,
I've just created an Access-Runtime package from one of my Access databases.
Everything works great in deploying it.
But... as you all know, the Access Runtime installs a version of MsAccess in
the C:\program files\CommonFiles\Microsoft Shared\Access
Runtime\Office10-directory...

If a user browses to this location, he is able to start msaccess.exe and
create a database. I want to prevent users from creating new databases from
this Runtime-location.

Is it possible to do so? Please help me :)

m.
 
Run-time version of Access does not allow creating a new database or
modifying the design of an existing database, AFAIK.
 
If a user is able to create a db from the Runtime exe then I suspect that
they also have the Retail version installed soemwhere on that machine.
Runtime and Retail are actually the same set of files. Registry entries tell
Access whether to function as Runtime or Retail on that machine. You can
tell Retail to "dumb down" and operate as Runtime with command line switches
when you open an app, but if both versions are installed I don't think there
is a way to prevent db creation outside of your application (and I
respectfully suggest you ask yourself if it is really any of your business:
they evidently have a license to do just that). When 2 copies of
msaccess.exe exist on the same machine, I doubt that Access cares which exe
file was used to start it: msaccess.exe is msaccess.exe and the machine
either has a Retail license or it doesn't. (I'm ignoring 97-2000-XP-03
version issues when I say that, of course).

If this really is a problem, I guess you could uninstall the Retail (which
might necessitate re-installing Runtime), but that seems pretty extreme.
 
Back
Top