Does Access have a run-time or similar packaging method? 1

[Shinken]

I haven't done much DBMS programming in about 10 years or so and am just getting used to Access (much easier than the older dBase, RBase, Fox, apps). I've developed an Access DBMS for use by 1 or 2 users in our office. How can I package it so that:

1. The forms are displayed in non-resizeable windows?

2. The users can't meddle with the Design of the form. Is there a run-time method of packaging the database?

Also, is there a way to modify it on my machine and transfer the forms, queries, etc to the user's machine without affecting the data/tables on their machine?

Thanks,

P

 

[Junior1544]

There is an access run-time... you can get it in the access developers edition... I don't know much about it though...

--James
junior1544@jmjpc.net
Life is change. To deny change is to deny life.

 

[nberryman]

OK, first the second question. If you select Tools, database utilities, database splitter.

This will split the MDB into two MDBs, the front and back end. All the tables live in the back end and everything else in the front end. This allows you to modify the design (exept table design) and distribute a new front end but retain the data in the backend.

The first question. Again Tools, Database utilities, Make MDE file. An MDE file is a compiled non editable database (Microsoft Database Executable). This will stop the users changing the design but as long as your forms allow they can still edit and add data.

Make the front end an MDE file and distribute this and you won't need to pack it with run time.

Neil Berryman
IT Trainer
neil_berryman@btopenworld.com

 

[Junior1544]

He's right that you wont need to distribute the run time, but that's not an executable file... if the user doesn't have access, they can't open the file. then they will either need access installed, or the run time...

--James
junior1544@jmjpc.net
Life is change. To deny change is to deny life.

 

[RiverGuy]

For the 3rd question, can you explain a bit more? Are you making a shared app, like on a LAN, or making clones of the same app for each user to run locally and edit their own data?