>>>>>>>>>>>>>>>>>>>>>
Thanks to both of you for opening my eyes more on buffering. To date, all I have been using was the BufferMode in the form PIMs, and nothing further. Now I have gone back and used the CURSORSETPROP() when adding/editing a record, followed with the TABLEUPDATE(.T.) when saving it.
>>>>>>>>>>>>>>>>>>>>>
As I mentioned to you on another message, be careful with TableUpdate(.T.). I mean, you should ceck the return value to see if you have any posting conflicts that must be resolved. (see Message #474711)


>>>>>>>>>>>>>>>>>>>>>
Ironically, I was getting away with this for over a year while the customer was running on a Novel network. Now, with the NT network, I was getting stung. Similarly, since the change of networks, the means of assigning Unique ID's to records had to be altered. Duplicate numbering sequences were cropping up when multiple users were adding the same type records. Is there something I should be looking out for when dealing with NT?
>>>>>>>>>>>>>>>>>>>>>
The system that works for me on assigning unique IDs, is to set up a counters table that has two fields, TableName and LastID. Whenever you need a new ID yiu call a funtion (like NewID(Alias()) passing the current alias or table name you want the ID for. The function seeks in the counters table. If it finds, increments and gives you the new ID for your table. If not found, adds the new record with the table name setting the counter to 1.