A
aemAndy
I'm working in a application that I did not create, but I have administrator
priviledges, so let me know if I need to tweak some settings.
The current database uses a fresh upload of data from another functional
area when we create our annual reports. I've already had problems with
people wanting to view historical data on the table that isn't kept.
I wanted to keep the old data around, so I went to the table, did a "save
as" and renamed the table (ex. was tblDataInfo, did a "save as" to keep a
copy as "tblDataInfo2003").
When it saves the table, it saves it as a linked table to the original, so
when I wiped the original table and loaded fresh data, it wiped out what I
had wanted to be the archived data table.
I don't see anything that allows me to "de-link" the tables without
completely removing one from existence.
Why would a "save as" be automatically linked? Or is this something the
original programmer did, and how can I disable this?
priviledges, so let me know if I need to tweak some settings.
The current database uses a fresh upload of data from another functional
area when we create our annual reports. I've already had problems with
people wanting to view historical data on the table that isn't kept.
I wanted to keep the old data around, so I went to the table, did a "save
as" and renamed the table (ex. was tblDataInfo, did a "save as" to keep a
copy as "tblDataInfo2003").
When it saves the table, it saves it as a linked table to the original, so
when I wiped the original table and loaded fresh data, it wiped out what I
had wanted to be the archived data table.
I don't see anything that allows me to "de-link" the tables without
completely removing one from existence.
Why would a "save as" be automatically linked? Or is this something the
original programmer did, and how can I disable this?