Hi Todd,

Re # 1, read chapter 17 "Programming for Shared Access" in the VFP6 Programmer's Guide. Many of the popular VFP books also contain discussion and examples on this topic; browse around in your local bookstore for any VFP5 or VFP6 book, or go to www.hentzenwerke.com for most of the VFP6-specific books.

Re # 2, have you tried "UNLOCK in cAlias", or "UNLOCK ALL"? If this doesn't work, probably the NOS has flagged the lock and won't release it until the workstation connection is reset, e.g. with a reboot.

BTW, optimistic buffering works well in many situations, and avoids some of these problems. If you can, you may want to rethink your need for pessimistic buffering.

HTH,
Rick


>As a self taught programmer, I have learned procedures and processes as they are need. For the most part, trail and error, 3rd party books, or Microsoft's meager help system has gotten me through. That was up till now.
>
>Problem 1
>---------
>To date, the few applications I have developed have been designed for use on a single system. My new project will require concurrent network access to tables. I have read about Multilocks, Reprocess, Locks, and Unlocks. Not much there but I have figured some of it out. This functionality seems to be very fundamental to the operations of a database system. Due to the lack resources (from what I have available now) I am asking for any help or code that anyone may have regarding table sharing, record locking and other network functions.
>
>Problem 2
>---------
>I was experimenting with some of the functions that I found in the wonderful Microsoft help books and ran into a quandary. We are planning on using a Pessimistic Locking scheme for adding/editing data in tables. If a user opens a table ,locks a record, and then crashes, the only way we have found to release the lock on the record is to reboot the system. Unlock (the command) only works on records you have locked. Is there some sort of master unlock command or code that will work around this problem?
>
>Thanks in advance for all your help.
>
>Todd Cottengim
>Alpine Land Information Services
>alpine@awwwsome.com