No, the term upsizing *usually* refers to moving data from a ms-access data
file to sql server.
I noticed when I changed something once the data was entered I would lose
all the info. grrrrrrrrr!
No, that should not happen at all. Of course, it is not clear what you mean
by lose all the info. You can most certainly add new fields to a table. For
sure the existing fields names should NOT be changed (well, you can change
them, but this means all your forms, and code etc. may have to be changed).
So, you are certainly free to add new tables. You are free to add new fields
to exiting tables, and in most cases these changes do not break, or cause
any problems with the existing application.
Once you add those new fields, you can bring up a form in design mode, and
then add those additional fields to the screen. In fact, a lot of use DO NOT
use the wizards to build a form, but simply open a blank form, and start
from scratch (we don't use the wizard). However, even forms built by the
wizard can be brought up in design mode.
Often, a form is based on query. So, if you add a few new fields to the
table, then you will NOT be able to add, or see those additional fields when
in the forms DESIGN VIEW. The solution in this case is to simply add the
additional fields to the forms underlying query also.
On the other had, perhaps you are taking about a production database, and
you need to work on the next great version while the users use, or work with
the existing version. In that case, what is done is that you split your
application in the data part (we call this the back end), and the
application part (the front end).
For info on that:
http://www.granite.ab.ca/access/splitapp.htm
http://www.microsoft.com/accessdev/articles/bapp97/chapters/ba15_3.htm