Big Picture question:
All transactions are tracked to a shift identifier.
App has a Close Shift function.
User on workstation 1 closes the shift.
User on workstation 2 has a form up that shows the current shift PRIOR to workstation 1 closing the shift.
Unless workstation 2 refreshes the form and underlying data, BEFORE performing a transaction, the transaction will be marked with the PREVIOUS shift's identifier.
I have several functions that are conceptually the same problem. I understand (or think I do), multiuser record locking, etc. but this seems to be more a matter of "big picture" approach to how I have designed the app.
I need suggestions or a better understanding. I have read all the posts on multiuser and read the VFP help on developing in a multiuser environment but nothing there seems to help.
Thanks,
John
All transactions are tracked to a shift identifier.
App has a Close Shift function.
User on workstation 1 closes the shift.
User on workstation 2 has a form up that shows the current shift PRIOR to workstation 1 closing the shift.
Unless workstation 2 refreshes the form and underlying data, BEFORE performing a transaction, the transaction will be marked with the PREVIOUS shift's identifier.
I have several functions that are conceptually the same problem. I understand (or think I do), multiuser record locking, etc. but this seems to be more a matter of "big picture" approach to how I have designed the app.
I need suggestions or a better understanding. I have read all the posts on multiuser and read the VFP help on developing in a multiuser environment but nothing there seems to help.
Thanks,
John