updating a split database

[weazer via AccessMonster.com]

I just recently split my database and I made a copy of the front and back end
and gave them a different name.

If I add queries, reports, tables etc. how do I replace the active front and
back end.

Do I change the names on my copy to match the original names and replace them
via copy?

I read a lot of posts on this subject but I am still confused.

Also, I tried to convert an access 2000 db to an access 1997 db and I get
getting errors - any ideas?

Thank you.

 

[Albert D.Kallal]

I just recently split my database and I made a copy of the front and back

end
and gave them a different name.

Hum, for what reason did you given them a different name?

For the most part, I do make a copy, and then place them in my "development"
machine, or often a development directory.

You the simply fire up the linked table manager..and link the front end (FE)
to the back end (BE). I explain this process
of have you HAVE to link to the copy of the back end in my article here

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

If I add queries, reports, tables etc. how do I replace the active front
and
back end.

Careful. You can add quires, you can add new forms. You can add new reports.
Up to this point, it is easy to deploy this new version with the new
changes. You simply re-link to the production back end. Then create a
mde..and distribute that new mde to all of you users.

However, any modifications to the data structures has to be done in the BE.
Either you write down your changes you made to your "copy" of the BE, and
then RIGHT before you deploy the new FE..you go and make the SAME
modifications to the BE. Another way is to simply ask everyone to go home,
or at least exit out of the application, and then you modify the BE (wither
way..you always had to kick everyone out when modifying the table
structures....at least now you can do this on a copy of the BE..and further
you are free to work on the new FE...which you could not do before
splitting).

Do I change the names on my copy to match the original names and replace
them
via copy?

Hum, as mentioned, for the most part I don't bother re-naming the files, and
it is best to keep them the same.....

Also, I tried to convert an access 2000 db to an access 1997 db and I get
getting errors - any ideas?

Well, if you plan to deploy the appcation as a acces97 application, you are
MUCH better off to develop in a97. If you develop in a2000, it is possible
that you will use one of MANY new features in a2000...and they will not work
in a97.

 

[weazer via AccessMonster.com]

Thank you for your help.

Would it cause a problem if I made changes to the front end on my PC which is
on my c drive (this is the active FE)?

Also, when you relink does it make another copy of the table with trhe new
link. After linking for the 2nd time I noticed the tables were listed again
with one set of arrows highlighted and the other set of arrows are not
highlighted.

Thanks again for your help.

 

[Albert D.Kallal]

Thank you for your help.

Would it cause a problem if I made changes to the front end on my PC which
is
on my c drive (this is the active FE)?

no, not at all. Each user has their own copy...so, you are free to work on
your copy.
However, as mentioned, each user likely get a mde...not a mdb. Further,
since you FE
linked to the live data...if you are testing some code to delete data..and
you mess up,
then you might trash the whole database. It certainly sounds like a big risk
to test
your application on live data while you develop..don't you think?

So, often, you will make a copy of the BE..and place that on your local
drive, and
then link to that during development..

Also, when you relink does it make another copy of the table with trhe new
link.

no, using the linked table manger simply lets you choose which back to link
to. This really the same as use a file->open in word, or excel.

This is a relatively short and quick process..and you should have little
problem linking to your live BE, or a copy of the BE.

You are simply using the linked table manger to select which back end to
link to.

After linking for the 2nd time I noticed the tables were listed again
with one set of arrows highlighted and the other set of arrows are not
highlighted.

Hum..the above makes no sense at all...somting is being done wrong here.
Perhaps you are using the import option...and that is wrong....

You will only use the split wizard once......and that is it...


After that...you used the linked table manager to re-link to a BE of your
choice....