Help with changing a field on a form to be able to update sporadically

[cjohnson]

Hi, I am new to access and have managed to create a form/ table to inventory pictures/furniture at my place of work. These items are randomly checked by our insurers and given more up to date insurance values, (can occur over many years)

What I want to be able to do is enter the currant data and then update as and when a valuation is done. But still be able to see the previous years data. almost like and excel table(?)



At the moment I have done it like this......

but realised that I will need to move the data every time we have an updated valuation so to keep the currant and most recent data at the top.

I am not sure if I have explained this well but difficult when I have muddled through to this point! hopefully someone can help

Thank you

[John_G]

You have a one-to-many relationship here. You will need two tables - one for the asset item details (the "one" side), and another for the valuations (the "Many" side)

The second table will have at least these fields:

Asset Number (from the Assets table)
Valuation Year
Value

and it could have all sorts of other data as well, such as valuation date, who the estimator was, comments, etc.

One-to-many relationships are typically worked with using a main form - subform arrangement.

Your screenshot shows a "repairs" tab. Repairs would also require a one-to-many relationship (One asset can have 0 to many repairs)

[Bob Fitz]

I agree with the comments made by John_G.

The attached db might help as a starter.

[cjohnson]

Thank you for your help will give it a go and fingers crossed I can make it work!

You have a one-to-many relationship here. You will need two tables - one for the asset item details (the "one" side), and another for the valuations (the "Many" side)

The second table will have at least these fields:

Asset Number (from the Assets table)
Valuation Year
Value

and it could have all sorts of other data as well, such as valuation date, who the estimator was, comments, etc.

One-to-many relationships are typically worked with using a main form - subform arrangement.

Your screenshot shows a "repairs" tab. Repairs would also require a one-to-many relationship (One asset can have 0 to many repairs)

[cjohnson]

Thank you for your example think I can muddle through with your advice.

Thank you