Updating a split database

Hi there

I've searched through the access forum and found several possible ways to do
this but I thought I'd ask for confirmation.

I have split my database and distributed to my users but I need to make some
updates/changes to the database. I need to modify three tables and its
associated forms. Also, I need to correct a button on one of my forms that
doesnt work.

Should I be working on the split database or the original database before it
was split?

Also, if I work on the split database, do I work on the front end or backend?

How do I get the new database changes to my users if they're currently
working on it?

Thank you in advance for your help.

On Sun, 18 Apr 2010 21:52:01 -0700, forest8
wrote:

Hi there

I've searched through the access forum and found several possible ways to do
this but I thought I'd ask for confirmation.

I have split my database and distributed to my users but I need to make some
updates/changes to the database. I need to modify three tables and its
associated forms. Also, I need to correct a button on one of my forms that
doesnt work.

Should I be working on the split database or the original database before it
was split?

Also, if I work on the split database, do I work on the front end or backend?

How do I get the new database changes to my users if they're currently
working on it?

Thank you in advance for your help.



You must make the table changes in the backend, because that's where the
tables are. If the users are already sharing the backend, you'll need to get
exclusive access to it to make the changes.

Form, report, query and code changes must be done in your own copy of the
frontend. You'll want to *delete* the links to any tables that you changed,
Compact and Repair the database, and use File... Get External Data... Link to
relink to them. Make the form changes after you have done so; then you can
distribute copies of the new frontend (or, better, a .mde file made from it)
to your users.

The orignal database is now useful for archival, not for much of anything
else.
--

John W. Vinson [MVP]

To make changes to fields and/or tables in the Back-End file then have
a look at the code in the Back End Update Utility at :-

http://www.rogersaccesslibrary.com/f...-89fzzb27.html

You may also need to re-link the front end to the back end at the
user's site automatically, the Back End Re-Linker code at this site
can do that.

If your clients are using a network you could try the Front End
Updater Utility on the same site. You would just email the client a
new version of the front-end file (zipped, of course) and tell them to
unzip it into the appropriate folder on their Server PC. The
documentation provided explains how to set it up.

HTH

Peter Hibbs.



On Sun, 18 Apr 2010 21:52:01 -0700, forest8
wrote:

Hi there

I've searched through the access forum and found several possible ways to do
this but I thought I'd ask for confirmation.

I have split my database and distributed to my users but I need to make some
updates/changes to the database. I need to modify three tables and its
associated forms. Also, I need to correct a button on one of my forms that
doesnt work.

Should I be working on the split database or the original database before it
was split?

Also, if I work on the split database, do I work on the front end or backend?

How do I get the new database changes to my users if they're currently
working on it?

Thank you in advance for your help.

I just did a change to automate the back-end to update (based on a new
version of the software).
I went with back-end update utility method that Peter recommended.
This one is also good:
http://home.gci.net/~mike-noel/Compa...reEM-About.htm

HTH,

--
Mark Andrews
RPT Software
http://www.rptsoftware.com
http://www.donationmanagementsoftware.com


"Peter Hibbs" wrote in message
...
To make changes to fields and/or tables in the Back-End file then have
a look at the code in the Back End Update Utility at :-

http://www.rogersaccesslibrary.com/f...-89fzzb27.html

You may also need to re-link the front end to the back end at the
user's site automatically, the Back End Re-Linker code at this site
can do that.

If your clients are using a network you could try the Front End
Updater Utility on the same site. You would just email the client a
new version of the front-end file (zipped, of course) and tell them to
unzip it into the appropriate folder on their Server PC. The
documentation provided explains how to set it up.

HTH

Peter Hibbs.



On Sun, 18 Apr 2010 21:52:01 -0700, forest8
wrote:

Hi there

I've searched through the access forum and found several possible ways to
do
this but I thought I'd ask for confirmation.

I have split my database and distributed to my users but I need to make
some
updates/changes to the database. I need to modify three tables and its
associated forms. Also, I need to correct a button on one of my forms that
doesnt work.

Should I be working on the split database or the original database before
it
was split?

Also, if I work on the split database, do I work on the front end or
backend?

How do I get the new database changes to my users if they're currently
working on it?

Thank you in advance for your help.

Hi again

I won't be able to get my split database from my users until the
administrator returns from holidays.

Can I work on my version of the database (BE and FE) and then somehow add to
the users' version when he sends it to me?

Thank you
Forest

"John W. Vinson" wrote:

On Sun, 18 Apr 2010 21:52:01 -0700, forest8
wrote:

Hi there

I've searched through the access forum and found several possible ways to do
this but I thought I'd ask for confirmation.

I have split my database and distributed to my users but I need to make some
updates/changes to the database. I need to modify three tables and its
associated forms. Also, I need to correct a button on one of my forms that
doesnt work.

Should I be working on the split database or the original database before it
was split?

Also, if I work on the split database, do I work on the front end or backend?

How do I get the new database changes to my users if they're currently
working on it?

Thank you in advance for your help.



You must make the table changes in the backend, because that's where the
tables are. If the users are already sharing the backend, you'll need to get
exclusive access to it to make the changes.

Form, report, query and code changes must be done in your own copy of the
frontend. You'll want to *delete* the links to any tables that you changed,
Compact and Repair the database, and use File... Get External Data... Link to
relink to them. Make the form changes after you have done so; then you can
distribute copies of the new frontend (or, better, a .mde file made from it)
to your users.

The orignal database is now useful for archival, not for much of anything
else.
--

John W. Vinson [MVP]
.

On Wed, 21 Apr 2010 12:56:01 -0700, forest8
wrote:

Hi again

I won't be able to get my split database from my users until the
administrator returns from holidays.

Can I work on my version of the database (BE and FE) and then somehow add to
the users' version when he sends it to me?

The frontend, sure; but the changes to the backend must be made in their
backend. That's where all their working information is! Your copy of the
backend (I presume) does not contain the information that they are entering,
so any changes that you make to its structure are irrelevant.

The only out would be to make the changes in your copy of the backend, and
then write a whole mess of append queries to let you link to their backend and
append all the data into the new backend.
--

John W. Vinson [MVP]