Time Based Data - Simple Approach (Access/SQL)

Time based data is important in many scenarios. Club memberships, University Courses, Prices, Taxes and many other types of data are valid

only for a certain time or date range.

In this video I show a simple approach to store such data in an Access database. Storing data does only make sense if you can query it too.

Of course, I cover how to query the data as well.

[neojumpy]

Fact is that the price information is an accounting information and just like the order quantity has to be stored histrosich.
Ur example fits better for picking standard values at the moment of creating positions rows. With ur construction u can even store price values for the future. Thanx 4 ur good structured video.

[Mladenac]

postgresql uses range types and exclusive indexes. much easier than using sql access

[wilsonfineart]

Since prices change over time, one might presume that it's not appropriate to keep pricing data in the inventory table.

[neilthornton]

In a lot of ways, ValidTo field is redundant. I work in Military units and lot of times I guessing a the date (DateAccurracy) and find the ValidTo date to be a tripping point. If you don’t use ValidTo, you do need a closing record (EOD End Of Data)