We have a 7 Workstation network running under windows 95 with a 5 user lan pack in OI3.5. Occassionally, users are overwriting rows in tables because the row is not being locked by an application form. An example of this is in the order entry form in which a sequential key generates the next order number. More than one user may show the same row key as the next available order no. on the form, which is reasonable, and most times one user will lock all other users out, with the others users then obtaining the next sequential key. However, occassionally, users seem to be able to enter data in the order form and when saving get the message. "Row exists, Overwrite?". We suspect there may be a limit to the number of locks available under Win 95 but do not know if or how we can increase this. Anyone got any ideas?

Your best bet it to write your own sequential lock logic yourself. On create/write/clear (depends on app flow), read and update the key. It's stored as %SK% in the dictionary.

Revelation's CompuServe Forum has a couple of programs to handle this, most with source code so they can easily be converted to OI.

[email protected]

Sprezzatura, Inc.

Thank-you for your response but shouldn't OI handle this. Also, I cannot get to the Compuserve Forum, so is there another one to get some examples of these routines to handle sequential key locking. My email address is [email protected] if this helps.

View this thread on the Works forum...