I have an Inventory table. In the main view I have a QOH_store that is a calculation of Count and Sold.

When I make a new layout that displays the QOH_store and the Sold Fields, the QOH_store field isnt updating automatically. I have to click in both fields to update the info. HOWEVER, just clicking one of those fields doesnt update both of them.

I thought maybe using the Relookup would help but it says that there are no fields that lookup values based on the Sold field, which is not true...

Why don't you use an unstored calc?

Using Count() would REQUIRE the field be unstored anyway.

Yes, but as far as i can tell, given the keyword "relookup" there, it's probably a lookup field, with a calc in it... Maybe using the word unstored was redundant though.

Using Count() would REQUIRE the field be unstored anyway.

Would it?

On a related field it would..

No, it would be the related field alone that requires the calculation to be unstored - whether you used Count() or not.

Isn't that what i was implying, or are you trying to get across the more general point that only making reference to a related field, unstored calc or global field will cause a calc field to be compulsorily unstored?

I don't know. I was nit-picking on LaRetta's statement. Using Count() has nothing to do with stored/unstored. Using a related field does. True, most of the time you would use Count() with a related field, but that doesn't mean Count() is the cause.

Since it seems that no one understands the situation described in the original post, I thought it was worth pointing out.

Lol, don't worry, I like you :

After all, LaRetta tried to nit-pick at my statement : .

I wonder where the OP's run off to anyway...

RvToy is either sitting to the side eating popcorn or figured FM might twist his/her mind too much (using us as example) and have abandoned the ship. Ha ha!

Michael. I made an assumption on Count(); thanks for catching that. FM only requires it be unstored if it references other records (within same table) or another table/file. I assumed because it was an aggregate function, it would need to be unstored but aggregate = unstored is INCORRECT! Much appreciated.

L

I thought maybe using the Relookup would help but it says that there are no fields that lookup values based on the Sold field, which is not true...

A Relookup needs to be applied to the related foreign key (MainID) which binds the relationship. Is that the Sold field? It couldn't be!