JackDanIce
Well-known Member
- Joined
- Feb 3, 2010
- Messages
- 9,922
- Office Version
- 365
- Platform
- Windows
Hi
I'm designing a database which has an Excel front-end and uses Access for data store.
Each save from Excel to Access is a normalised table showing data for: A (one) Client which has 0 or more Jobs and where each Job has 0 or more Transactions
If I need to reload previous saved states for a given job or Client any tips/suggestions on how to structure the data?
I'm assuming I'll need a time-stamp field (Excel or Access generated) when data is appended to a [Transactions?] table
Also, if a transaction has value 10, saved with time stamp Today and tomorrow, value remains 10 but saved with tomorrow's time stamp, over time, this would create a large amount of data where only the time stamp field is changing.
Is there a better solution to save relevant change and allow roll back to previous save points?
TIA,
Jack
I'm designing a database which has an Excel front-end and uses Access for data store.
Each save from Excel to Access is a normalised table showing data for: A (one) Client which has 0 or more Jobs and where each Job has 0 or more Transactions
If I need to reload previous saved states for a given job or Client any tips/suggestions on how to structure the data?
I'm assuming I'll need a time-stamp field (Excel or Access generated) when data is appended to a [Transactions?] table
Also, if a transaction has value 10, saved with time stamp Today and tomorrow, value remains 10 but saved with tomorrow's time stamp, over time, this would create a large amount of data where only the time stamp field is changing.
Is there a better solution to save relevant change and allow roll back to previous save points?
TIA,
Jack