By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,124 Members | 2,027 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,124 IT Pros & Developers. It's quick & easy.

Updating Forms

P: n/a
I've built a simple DB and I'm having my users test it at a different
location running on a single workstation. Mean while I'm making
changes to the forms and reports on my workstation. How do I update
those changes to their database without losing data in the tables? Do
I copy and paste the specific form into the test DB?
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On 3 Feb 2004 23:00:23 -0800 in comp.databases.ms-access,
ma*******@byu.edu (Mark Lees) wrote:
I've built a simple DB and I'm having my users test it at a different
location running on a single workstation. Mean while I'm making
changes to the forms and reports on my workstation. How do I update
those changes to their database without losing data in the tables? Do
I copy and paste the specific form into the test DB?


The usual method is to split the database into front-end forms,
queries, reports and code and another one with just the tables in,
then just replace the front end. There is a wizard to help you with
this and a linked table manager for re-linking the tables in a
different location.
--
A)bort, R)etry, I)nfluence with large hammer.
Nov 12 '05 #2

P: n/a
Trevor Best <bouncer@localhost> wrote in message

The usual method is to split the database into front-end forms,
queries, reports and code and another one with just the tables in,
then just replace the front end. There is a wizard to help you with
this and a linked table manager for re-linking the tables in a
different location.


Trevor:

Thanks. A few questions though. 1. Can you split a database on a
single workstation? (I'm assuming so) 2. Where does the back end get
stored (default database folder?). How do you actually replace the
front end?

Thanks

Mark
Nov 12 '05 #3

P: n/a
On 5 Feb 2004 10:35:33 -0800 in comp.databases.ms-access,
ma*******@byu.edu (Mark Lees) wrote:
Trevor Best <bouncer@localhost> wrote in message

The usual method is to split the database into front-end forms,
queries, reports and code and another one with just the tables in,
then just replace the front end. There is a wizard to help you with
this and a linked table manager for re-linking the tables in a
different location.
Trevor:

Thanks. A few questions though. 1. Can you split a database on a
single workstation? (I'm assuming so)


Yes.
2. Where does the back end get
stored (default database folder?).
Anywhere you want, use the linked table manager to tell the front-end
where the back-end is.
How do you actually replace the
front end?


You make the changes in your development PC, copy the MDB over to the
client's PC, since the back-end is separate, you don't overwrite their
data in doing so.

--
A)bort, R)etry, I)nfluence with large hammer.
Nov 12 '05 #4

P: n/a
Trevor:

I really appreciate the help!
Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.