<< In your point #2 though, wouldn't you run into the possibilty of editingsomeone else's insert using the same argument you made in #1? I would thinkit's safer to use the intermediate variable. Or, can you EDIT USING fwo_formWHERE COUNT = INSERT? >>
Yes, you can issue EDIT USING fwo_form WHERE COUNT = INSERT or use the WHERE COUNT = INSERT anywhere you would use a WHERE clause. << If so, then the question is: How long is COUNT = INSERT valid? Obviouslytill the next insert. Will it survive a RETURN? Will it carry to anotherpiece of code? Is it valid throughout an R:Base session for that user? How 'bout till the next session of R:Base? Do other SQL commands reset/nullit? >> Obviously, nothing I say should be taken as a definitive answer, but here's my understanding: 1. R:Base will remember the last record inserted for each table in the database separately. 2. Each user's INSERT records are remembered separately (a subsequent insert by a different user will _not_ cause your session to get mixed up about which record you inserted). 3. R:Base will remember the INSERT record for each table for the duration of the session. You don't have to worry about RETURNs, etc. 4. If you try to use COUNT = INSERT _before_ inserting a record into the table in question, you will get a record but I have no idea which one. -- Larry
