Best way to install changes

[Sarah]

I made changes to many forms and reports in one of my customer's systems. Is
it best to import the forms and reports that I made changes to into my
customer's system that has the complete data or is it best to import the
complete data into the system copy that I made all the changes to?

As usual, thanks for your help.

Sarah

 

[Klatuu]

Import the objects into the client's database.
Why are you not using a split database?

 

[Sarah]

What is a split database?

Sarah

Import the objects into the client's database.
Why are you not using a split database?

 

[Klatuu]

A split database is where all your data resides in one mdb and all other
objects(queries, forms, reports, modules) are in another mdb. The mdb with
the data is referred to as the Back End database (BE) and the other is the
Front End database (FE). You do this using the database splitter
(Tools->Database Utilities->Database Splitter). This will move all your data
tables to another dabase and give it the same name with _be appended to it.
For example, if your current database were named MyDataBase.mdb, it would
create MyDataBase_be.mdb.
Now the FE datbase instead of having its own tables, will use linked tables,
in otherwords, a reference to the tables in the BE database. If you move the
BE database, you will have to relink the data using the Linked Table Manager
(Tools->Database Utilities->Linked Table Manager.
This is the proper way to install an Access application. Do some reading
and research on it.

 

[Sarah]

Thank you for the explanation. I like the split idea. Are there any risks
to using split databases?

Sarah

 

[Klatuu]

There are more risks if you don't.
First, it will eliminate the modification question you started with. You
can replace the entire FE without worrying about the state of the data.
If you are in a multiuser environment, each user should have their own copy
of the FE on their own computer, with their links set to the BE. Note here,
always use UNC drive mapping so that there will be no problem with users
having different drive letters. (Not F:\SomeDirectory\AccessData, but
\\MyServerName\SomeDirectory\Access Data)
It will reduce corruption problems,
I could go on and on. If you do some research, you will find that this is
the recommended way to do Access.
Good Luck

 

[Sarah]

Klatuu,

Thanks for all you help.

Sarah

There are more risks if you don't.
First, it will eliminate the modification question you started with. You
can replace the entire FE without worrying about the state of the data.
If you are in a multiuser environment, each user should have their own copy
of the FE on their own computer, with their links set to the BE. Note here,
always use UNC drive mapping so that there will be no problem with users
having different drive letters. (Not F:\SomeDirectory\AccessData, but
\\MyServerName\SomeDirectory\Access Data)
It will reduce corruption problems,
I could go on and on. If you do some research, you will find that this is
the recommended way to do Access.
Good Luck