If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Setup ?
Hi, I am trying to create an access database that has historical data and new
data is imported in monthly. I need it to be able to check each time if it's a new member before it dumps into the data. If it's new it needs to be tagged new? And then I need to be be able to run comparisons on future data to that first event? What's the best way to clone the records together? 1) Do I create a working table (holds everything) 2) Create a temp table (monthly table) 3) Somehow run something that checks and tags? How do I do this? 4) Then append? -- Thank you in advance!!!! |
#2
|
|||
|
|||
Setup ?
On Tue, 23 Mar 2010 15:46:01 -0700, daisy
wrote: Hi, I am trying to create an access database that has historical data and new data is imported in monthly. I need it to be able to check each time if it's a new member before it dumps into the data. If it's new it needs to be tagged new? And then I need to be be able to run comparisons on future data to that first event? What's the best way to clone the records together? 1) Do I create a working table (holds everything) 2) Create a temp table (monthly table) 3) Somehow run something that checks and tags? How do I do this? 4) Then append? Depends. What are you importing *from*? A text file, a spreadsheet, another Access database table, something else? What constitutes a "new" record? Do you have a unique primary key in your table? in the import? If a record has an identical unique key but different data, do you want to overwrite the existing data, add a new record, generate a warning, or what? More info please! -- John W. Vinson [MVP] |
#3
|
|||
|
|||
Setup ?
We'll be importing from Excel into Access. The Name would be the commonality
between them. A new record would show up if they've renewed or added on to their contract. We want to be able to tag new deals and be able to compare new events with their older events? Thank you!!! -- Thank you in advance!!!! "John W. Vinson" wrote: On Tue, 23 Mar 2010 15:46:01 -0700, daisy wrote: Hi, I am trying to create an access database that has historical data and new data is imported in monthly. I need it to be able to check each time if it's a new member before it dumps into the data. If it's new it needs to be tagged new? And then I need to be be able to run comparisons on future data to that first event? What's the best way to clone the records together? 1) Do I create a working table (holds everything) 2) Create a temp table (monthly table) 3) Somehow run something that checks and tags? How do I do this? 4) Then append? Depends. What are you importing *from*? A text file, a spreadsheet, another Access database table, something else? What constitutes a "new" record? Do you have a unique primary key in your table? in the import? If a record has an identical unique key but different data, do you want to overwrite the existing data, add a new record, generate a warning, or what? More info please! -- John W. Vinson [MVP] . |
#4
|
|||
|
|||
Setup ?
On Wed, 24 Mar 2010 13:18:01 -0700, daisy
wrote: We'll be importing from Excel into Access. The Name would be the commonality between them. A new record would show up if they've renewed or added on to their contract. We want to be able to tag new deals and be able to compare new events with their older events? Thank you!!! Again: You can see your table and your spreadsheet. I cannot. I have no idea what a "contract" or a "deal" or an "event" is, or how they would be represented in your data, or how you would ascertain that one is new and another one isn't. Please post a field description of your Access table and (if it's not the same) your spreadsheet, with the fieldnames, datatype, and significance, and how a new whatever can be identified. Do note that Name is a reserved word and you should not use Name as the Name of a field; and that people's names are *terrible* linking fields (they're not unique; I know three men named Fred Brown, right here in little Parma). -- John W. Vinson [MVP] |
#5
|
|||
|
|||
Setup ?
Hi John,
I'll abbreviate and not include everything - They would be considered a new customer if they are not already in the table. It would be an addt'l event if it was a Invoice that was in addition to the new event, or annual renewal etc... B_Qtr InvoiceNo Event (this is the one that needs tagged) Cust_Name EffDt EndDt Total_Invoice Thanks! -- Thank you in advance!!!! "John W. Vinson" wrote: On Wed, 24 Mar 2010 13:18:01 -0700, daisy wrote: We'll be importing from Excel into Access. The Name would be the commonality between them. A new record would show up if they've renewed or added on to their contract. We want to be able to tag new deals and be able to compare new events with their older events? Thank you!!! Again: You can see your table and your spreadsheet. I cannot. I have no idea what a "contract" or a "deal" or an "event" is, or how they would be represented in your data, or how you would ascertain that one is new and another one isn't. Please post a field description of your Access table and (if it's not the same) your spreadsheet, with the fieldnames, datatype, and significance, and how a new whatever can be identified. Do note that Name is a reserved word and you should not use Name as the Name of a field; and that people's names are *terrible* linking fields (they're not unique; I know three men named Fred Brown, right here in little Parma). -- John W. Vinson [MVP] . |
Thread Tools | |
Display Modes | |
|
|