>>>>>Is there a reason that you are not using "INSERT INTO tablename ..." to add records?
>>>>
>>>>Hi Larry, have not heard from you in a while...
>>>>I am using APPEND BLANK with table buffering, is it preferably to use INSERT INTO with table buffering?
>>>>:)))))
>>>
>>>insert into is preferrable almost all the time
>>
>>How do I use INSERT INTO in code with table buffering.
>>Would you please give me a small example?
>>:))
>Should be no different than without table buffering. One possiblilty is to have a form with objects tied to memvars with same names as table fields. Input values, then with an "OK" button...
>INSERT INTO tablename FROM MEMVAR
>and when you are ready to commit the changes, perhaps another button called "Save", you issue your tableupdate comand.

thanks Larry - I will try this. please excuse me if this is a dup messaage.
Without using buffering everything is working good, but when I APPEND BLANK,
the record pointer to going to the last record instead of adding a blank
record at the end. Do you know why? thanks
also, once you told me how to add. You said to use up all the deleted
records and then append blank. In a single user system, I do not see
why you should use buffering at all. If the users aborts, just delete the
record and use it the next time the user wants to add. What to you think?
You can always APPEND BLANK OR INSERT INTO for adding.
I did try using INSERT INTO like to said, but I got a messsage saying I needed
to be in exclusive mood.
please comment :)))