'Fly-away' records and SQL
What is the exceptable way to handle 'fly-away' records when working
with a TQuery and a grid? TQuery doesn't provide a findKey method for
query objects and I'm not to keen on using the filter property because
I'm sing it for something else besides a bit of a pain.
It's like:
1. copy current filter to string
2. Turn filter off.
3. Set new filter string
4. do findFirst (ornext) implicitly turning on filter then off
5. set old filter back
6. turn filter back on.
My big problem is that my key is generated by the Oracle server after
inserting a record which means I don't know the key before posting. A
Paradox-style 'postRecord' would be cool which post and stays with the
record. Anybody have any advice? Thanks
--
John Parrott
Elysium Financial Systems
s...@interlog.com
http://www.interlog.com/~spo