Add data to a table and store it for later use

[Irina]

Hello,
I am new to the databases and the database in access that I am creating is
linked to a paradox database. I have one table that I update with all the
information from the linked tables for reports. The users want to add new
information to the blank fields in the table, but to synch my access database
with paradox one, I delete the table everytime. I am wondering how I can save
the information that users are adding for reports and not have the data
overwritten during sychronization.
Does anyone have any suggestions?

 

[Jeanette Cunningham]

Hi Irina,

This is not easy for someone new to databases.
Here is one way to do this.
Import the paradox data into an intermediate table which we can call a
staging table.
Then you use a query to extract only the new records from the staging
table - by new records I mean those added to the Paradox database since you
last imported the data from Paradox, and add these new records to your
existing table.

This way you are only adding the new records to your existing table, and not
overwriting the data that users had entered in the blank fields for your
existing data.

I assume that the new data you import from Paradox has completely new
records in it - that there are no changes to the Paradox data that you
imported yesterday.

Post back if this doesn't fit your situation.

Jeanette Cunningham

 

[John W. Vinson]

Hello,
I am new to the databases and the database in access that I am creating is
linked to a paradox database. I have one table that I update with all the
information from the linked tables for reports. The users want to add new
information to the blank fields in the table, but to synch my access database
with paradox one, I delete the table everytime. I am wondering how I can save
the information that users are adding for reports and not have the data
overwritten during sychronization.
Does anyone have any suggestions?

Do note that it is emphatically NOT necessary to create a new table based on
linking data from other tables, in order to create a Report.

Reports can be (and typically are) based on Queries, usually multitable
queries. These may well be linked tables.

You *might* have reasons such as performance and speed to require copying the
data to a local table - but try basing your Report on a query linking the
Paradox tables to a local table containing the user-entered data.

John W. Vinson [MVP]