>>>>OK I have one free table in my application that is shared with other applications (VFP and none VFP). This file is sitting on the netware drive and needs to be updated everytime a person runs my app. The file represents a login/logout file. So I need a strategy on locking the free table and updating the user record. Can anyone help on a bullit proof/non deadly embrace way of updating the multi-user free table on a netware drive. Thanks In Advance
>>>
>>>I guess I'm missing something? If its peruser login/logout why do you need to lock a record? Only that person should be on that record or they will be adding a new record. If I follow?
>>>
>>>Jeff
>>
>>The file is used to log a person in and then when they exit the app to log them out. So if the person logs in the a new record is added to the shared free table, when they leave the record is marked for deletion. In order to add a record to the free table (append blank) the table is locked for a short time, if another user tries at the same time to log in then the file is locked and they receive an error message.
>
>I think instead of append blank I would look at insert into. I know that you would be using UGH "memvars" but that way no lock should be needed. Right? or have I lost it completly?
>
>Jeff

That is my basic question, this being a free table and not associated with a database, what locks and what does not? How can I add new records/delete old records without affecting another user who may be trying to log in or out at that exact same moment. So I need a locking strategy for a free table or commands that are 100% non locking to add and mark records for deletion.