Database Runtime Question

[Rick Brandt]

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
Access to
view the database. My question is, when the runtime is created and
installed on the PCs that need it, if I need to add or make changes to the
database will the users with the runtime program be able to see these
changes or would
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.

 

[MFulton via AccessMonster.com]

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 Access to
view the database. My question is, when the runtime is created and installed
on the PCs that need it, if I need to add or make changes to the database
will the users with the runtime program be able to see these changes or would
I need to create a new runtime for them to see the changes? Thanks in
advance for your responses, they are appreciated

 

[MFulton via AccessMonster.com]

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

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.

 

[Daniel Pineault]

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.

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

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.

--



.

 

[Rick Brandt]

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

If you have all users opening the same shared file (bad practice) then you
cannot make any changes to the design while people are using it, at least
not since Access 97. If you made changes while everyone was out of the app
then they would see them when they next open the file.

In a version of Access old enough to allow design changes while people are
using the app (VERY BAD PRACTICE), the user might see the changes without
closing and re-opening the file, but I'm not sure if the behavior was
consistent.

As Daniel points out in his response you should always split your app when
you have multiple users and give each user a separate (usually local) copy
of the front end and only the file containing the tables is shared. Then
you would distribute new front end files after changes are made. To do
otherwise runs the risk of file corruption.

 

[MikeR]

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

I think there's some confusion about what a "runtime" is, the front-end (if the DB is
split) or the bit from MS so that you don't need Access installed.

Mike