>>I've read the old threads so I know that this has been discussed -- could somebody just help me clarify my thoughts...
>>
>>Is it true to say that when using table buffering, performing a SQL Select on the buffered data will always result in the oldval() values of the table?? Is there ANY way around this?
>>
>>Thanks,
>>Valerie
>
>Valerie, I don't think there is a way around it, because you have to clear the data out of your local buffers before the SQL can see it. If you're querying on a table you're also editing, just add a tableupdate() before the query (or requery).
>
>Barbara

Thanks Barbara. Using the tableupdate() is what I was trying to avoid, because I'd like to give my users the opportunity to run the reports based on their edited changes -- without commiting to them. I am very partial to using SQL Selects to create temporary cursors on which to base my reports, so that's how they all work (rather than creating relationships on multiple tables). I also have reports running from other forms providing other options.

Maybe I can combine the Report forms with every other data entry form as big form sets -- this would, at least, enable me to use the same data session -- wouldn't it? I know I would have to give up my SQL cursors for reports ... so it may not work anyway, but I can give it a shot.

Valerie