Updating Forms

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?

On 3 Feb 2004 23:00:23 -0800 in comp.databases.ms-access,
mark_lees@byu.edu (Mark Lees) wrote:
[color=blue]
>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?[/color]

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.

Trevor Best <bouncer@localhost> wrote in message[color=blue]
>
> 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.[/color]

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

On 5 Feb 2004 10:35:33 -0800 in comp.databases.ms-access,
mark_lees@byu.edu (Mark Lees) wrote:
[color=blue]
>Trevor Best <bouncer@localhost> wrote in message[color=green]
>>
>> 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.[/color]
>
>Trevor:
>
>Thanks. A few questions though. 1. Can you split a database on a
>single workstation? (I'm assuming so)[/color]

Yes.
[color=blue]
>2. Where does the back end get
>stored (default database folder?).[/color]

Anywhere you want, use the linked table manager to tell the front-end
where the back-end is.
[color=blue]
> How do you actually replace the
>front end?[/color]

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.

Trevor:

I really appreciate the help!