I'm putting the finishing touches on a multi-user program that uses a centralised dbc. The main data entry portion contains 5 tabs. Upon .activate of each tab the necessary tables are buffered. I get no problems when I test the system myself, however, we've been running into problems with data not being saved. Now, to change data you must first make your change... then all tabs, buttons, etc, are disabled and the user MUST either use the save button (performs table updates on all necessary tables depending on the current tab) or use the revert button. It all appears very solid, however, as I said... once many users get in on the system new records they've created are not being retained.... and I believe this only pertains to new records... not modified records. I'm using pessimistic buffering. These problems also only pertain to pessimistic table buffering as opposed to p.row buffering. All users should theoretically not have records open that another user does (because they're not assigned to that record) but it is possible.

Any suggestions? Should I post some code?

-JM