>>Like paddeling upstream. Grids are bound to data and an array is a memory element.
>>
>>USE the Force Luke! Sure you can probably do tons of custom code but ??? Why?
>>
>>I try to follow the KISS principle. What you are suggesting deviates from it.
>>
>>JMHO.
>
>
>I'm not understanding how you deal with the unsaved data in the table buffer for the view. I know that with a sufficent number of TABLEREVERT calls I can make it work, but that is anything but simple.
>
>I have a table buffer already in place on this form to handle the item detail updates. I thought you were advising me that two table buffers spelled trouble.
>
>What am I missing?
>
>Peter


Did you not say that this was display data? If so what are unsaved issues? You are not pasting back to the server the "running balance" are you? Otherwise you see it and poof its in the bit bucket when closed.

I work with SBT at the work place. It is very array intensive and I HATE them or SBT's implementation of them. Just about everything is array driven in SBT and VFP or FPW2.6 did such a fine job with base data. Let me knock SBT one last time, who in their right mind would design reports that are filled via arrays?

SET SBT BASHING OFF

So lets get back to the basics here. You need a grid to display data from some sort of "ledger" where the starting "balance" is dynamic. You want to update the balance's VALUE per transaction in the ledger system.

Are you going to allow this grid system to accept new transactions, such as credits, adjustments, or other?

Please show me how >> I know that with a sufficent number of TABLEREVERT calls I can make it work, but that is anything but simple.<< this is necessary?

__Stephen