Mykol

I have read so must about the similarities and differences of these two funtions that I'm confused again. I don't know if I have ever read the answer to my question or not, but, Which of those calculations will return a date and then NOT update it? I have a calculation that is supposed to return the current date when a number is entered in another field. The date isn't supposed to change after that. If someone can explain this to me along with what storage options should be set, I would be most appreciative. Cheers, Mykol

Brilliant! I was just missing that last piece. It never dawned on me to make the calc fields to relate to each other. After that, it was all magic. Thanks a ton. Mykol

The two fields that relate to each other are designation and edition. The designation I could see making a self join relationship, but since I want the previous edition, shouldn't there be a calculation that has the last edition number and then relate Edition Number to Previous Edition Number? This way I could make the Previous Material number show up in a lookup field. I'm not sure if I'm getting this right. I've never gotten the total concept of self-join relationships.

The two fields that relate to each other are designation and edition. The designation I could see making a self join relationship, but since I want the previous edition, shouldn't there be a calculation that has the last edition number and then relate edition number to previous edition number? I'm not sure if I'm getting this right. I've never gotten the total concept of self-join relationships.

I have a database I have created that lists all of our standards. It has past and current editions. When I create a new record, I would like certain fields to reference the material (part) numbers from the previous edition so I know which ones to take down from our online store. Is there a way to make fields reference other fields in other records based on certain criteria?