Hi,

You should be able to create a runtime package, just containing the
necessary files, ie Access runtime, but you run the risk of not having all
the necessary files available to the application unless you specify a
database.

I would recommend having a split database, ie backend/fronend. The backend
would contain the tables, and the frontend all other objects, you could
then using linked tables, link the backend to the frontend, and then create
a runtime application including this database, and install this on all
machine who need it.

This will mean that all users can update the same backend, but also you
will then ensure the all necessary dlls and reference libraries are
available to the user.

I hope this is of some help.

regards

Mark

This information is provided "as is", and expresses no warranties or
confers no rights.