>Hiya Jim ---
>
>JimB is correct (as usual). Derived values should be dynamic, meaning they should be recalculated as required and not stored. You may wish to create a parameterized view that SUM()s your YTD values for a given customer (the parameter being the customer primary key) and include that view in the dataenvironment of the applicable form.....*or*, if there is a tier issue, you can also have a YTDCust method in an application or business object which runs a query and returns a value.

Hey John!

Thanks for the response.

I'm gonna play with this a little and see what kind of results I get staying with Normalized data. I didn't consider using views as you suggested. I don't use views much, so excuse my questions if they come off sounding ignorant. If I'm using databound controls to a table, how do I get the form to rerun the query behind the view when I move to another customer (I'm assuming the control in question is data bound to the view)? How do I relay the current customer as the new parameter for the view when I do navigate?

BTW, there aren't any tiered issues here, but if there where I guess I don't understand why I would need a seperate app object to perform this logic. Why couldn't I use a remote view or provide logic in a method of the form?


Thanks in advance!