Search results

Brian, I really appreciate you posting that example, thank you for your assistance. Thank you for pointing out the issue of normalisation. I'm not sure what I can do remedy this given the nature of the data, hopefully it doesn't come back to haunt me. Cheers, -Mark

I would have to know more about your data to say how to uniquely identify the rows in Excel.

You do bring up an excellent point though now that I think about it more. Perhaps I can implement an operational solution such as deleting records from Table1 once all necessary operations have been performed on it, everything has been QC'd, and the data is more than 2 years old or something...

I forgot to mention that I need to preserve all the data in Table1 because it is used for multiple things - not just the scenario I mention.

I think my structure is correct. Table1 contains a time series of stream heights collected by stage recorders at various stream sites. I use a combo ID of the SiteID and DateTime to uniquely identify each record - there can never be 2 simultaneous stages at the same site. Table2 is the header...

You need someway of uniquely identifying records in your excel table. Once you do this, Access will automatically only add the "new stuff". That is the glory of the append. Does this make sense?

Excellent. Thanks a million. It will be interesting to see how long this takes once Table1 has years and years of data - millions or even tens of millions of records. Any tips for optimizing this once it gets huge?

Awesome! Thanks for such a quick reply!!!

I wish to use a date time stamp as the join between 2 tables in order to perform various queries. My issue is this: Table1 - this is a time series table, has date time stamps that may be in any interval (every 15 minutes, every 30 minutes, or no consistent interval at all). This table has...