D
DaleP
In the good old days, it was possible to append data from an excel spreadsheet that had some fields not matching the destination table. Without a whimper, Access 2.0 would add data from the fields that matched those in the Table and ignore the others
Is it possible to force the Office 2000 Access to behave this way
I am assisting someone who is using pivot table operations to summarize only a portion of monthly expenditure data from a complex accounting system. The problem is that some new codes used in the system get added from one month to the next; resulting in new fields popping up in the pivot tables. It would be helpful if Access could "comb" out the new fields and append the pertinent data fields to a static table
If one of the new Fields did become important, this person could simply add it to the design of the Access Table and continue updating the existing spreadsheet via Macro code in Excel.
Dale Pric
(e-mail address removed)
Is it possible to force the Office 2000 Access to behave this way
I am assisting someone who is using pivot table operations to summarize only a portion of monthly expenditure data from a complex accounting system. The problem is that some new codes used in the system get added from one month to the next; resulting in new fields popping up in the pivot tables. It would be helpful if Access could "comb" out the new fields and append the pertinent data fields to a static table
If one of the new Fields did become important, this person could simply add it to the design of the Access Table and continue updating the existing spreadsheet via Macro code in Excel.
Dale Pric
(e-mail address removed)