Calculation fields causing problems with SQL queries...

[angelleye]

I'm trying to connect to FM via ODBC. This normally works great, but I've run into an issue where one of the fields I need returned is a calculated field. As such, it cannot be indexed, and that calculation causes a very slow response when working with this particular data selection.

Qty_Available is the field I need returned. It calculates the value based on Qty_Received - Qty_Sold. If create a Qty_Available2 field that is not a calculation field is there a way to have it automatically always have the value that Qty_Available has?

This way I could use the second field in my SQL and since it's not a calculation field it will hopefully be fast. I need it to always match the calculated field, though.

Any information would be greatly appreciated. Thanks!

[BobWeaver]

Calculated fields can be indexed unless they reference a field from another table or a global field. If that's your situation, then you can create a standard field with the autoenter option set to a calculated value. Uncheck the "do not replace" option in the autoenter dialog.