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

Updating code/forms on working database while keeping data intact.

P: n/a
RC
I am updating/improving a working database for a non-profit
organization. I am thinking of making a copy of the database at the
office, bringing the copy to my house, making the changes and then
copying the new/improved database back to the hard drive of the PC at
the office. While I am working on the copy of the database at home,
the database has data being entered into it at the office.

My question is: how can I copy the new database back to the PC at the
office and still keep the data that has been entered while I was
working on the database? Almost all of the data that is entered goes
into one table. Can I --copy/export/set that table aside-- , install
the new database and then pull that table into the new database? I am
not familiar with importing and exporting and I don't know if it works
for individual tables. I am looking for a sort of "best practices"
way to make these updates/improvements.

Thanks in advance for your help, tips and advice.
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Split the database into two:
- back end, contains tables only;
- front end, links tables, and has all other objects.
You can then update the front end without overwriting the b.e.

There is a splitter built in:
Tools | Database Utilities | Splitter

We have used this technique since version 1 of Access, and never even
consider developing any other way. More information:
http://allenbrowne.com/ser-01.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"RC" <rc*********@yahoo.com> wrote in message
news:3c**************************@posting.google.c om...
I am updating/improving a working database for a non-profit
organization. I am thinking of making a copy of the database at the
office, bringing the copy to my house, making the changes and then
copying the new/improved database back to the hard drive of the PC at
the office. While I am working on the copy of the database at home,
the database has data being entered into it at the office.

My question is: how can I copy the new database back to the PC at the
office and still keep the data that has been entered while I was
working on the database? Almost all of the data that is entered goes
into one table. Can I --copy/export/set that table aside-- , install
the new database and then pull that table into the new database? I am
not familiar with importing and exporting and I don't know if it works
for individual tables. I am looking for a sort of "best practices"
way to make these updates/improvements.

Thanks in advance for your help, tips and advice.

Nov 12 '05 #2

P: n/a
RC
Thank You! An easy and elegant solution. Fabulous. I will read up
on this Splitter Utility. It sounds perfect.

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message news:<40***********************@freenews.iinet.net .au>...
Split the database into two:
- back end, contains tables only;
- front end, links tables, and has all other objects.
You can then update the front end without overwriting the b.e.

There is a splitter built in:
Tools | Database Utilities | Splitter

We have used this technique since version 1 of Access, and never even
consider developing any other way. More information:
http://allenbrowne.com/ser-01.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"RC" <rc*********@yahoo.com> wrote in message
news:3c**************************@posting.google.c om...
I am updating/improving a working database for a non-profit
organization. I am thinking of making a copy of the database at the
office, bringing the copy to my house, making the changes and then
copying the new/improved database back to the hard drive of the PC at
the office. While I am working on the copy of the database at home,
the database has data being entered into it at the office.

My question is: how can I copy the new database back to the PC at the
office and still keep the data that has been entered while I was
working on the database? Almost all of the data that is entered goes
into one table. Can I --copy/export/set that table aside-- , install
the new database and then pull that table into the new database? I am
not familiar with importing and exporting and I don't know if it works
for individual tables. I am looking for a sort of "best practices"
way to make these updates/improvements.

Thanks in advance for your help, tips and advice.

Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.