In a networked environment, the db is split into 2 parts (front-end and
back-end). The back-end, which houses the data, is place on a central server
that everyone has access to.
The front-end, which house your forms-reports----the gui, is distributed to
each user so that they have their own copy on their on pc.

So with this in mind, if you make updates to your database (front-end ---
add a button), then you will need to re-distribute the front-end to all your
users.

There are ways to automate this process (ie: see Tony Toew's autofeupdater),
but in a nutshell that is the process.
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.



"MFulton via AccessMonster.com" wrote:

So basically once the runtime is installed, runtime users will have access to
any changes made to the actual database as they are made. For example, lets
say I added a new button to a form, would they instantly see the new button
or would the runtime user have to close and reopen the runtime. Thanks for
your responses

Rick Brandt wrote:
I am designing a database in Access 2003. It is almost complete other
then the fact I need to create a runtime for it to enable PCs without
[quoted text clipped - 5 lines]
I need to create a new runtime for them to see the changes? Thanks in
advance for your responses, they are appreciated

Once they have the runtime installed, updates are simply a matter of giving
them updated Access files (MDB/MDE). In that sense it is no different than
using regular Access.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/201003/1

.