Multiuser Considerations
Because Sage 300 has the capacity to run on local area networks, there may be times when more than one user needs to use the same Project and Job Costing database.
Sage 300 has two basic rules for protecting data integrity when workstations share the same data:
- Make sure no more than one user is working in the same batch at the same time.
- Make sure no one is working in a batch that you want to print or post.
Sage 300 uses the following record access types to protect data in a multiuser environment:
Global Locks
The PJC Options screen locks out all other users from Project and Job Costing until processing is finished.
If other users are working in Project and Job Costing while you attempt to Save project and Job Costing options, Project and Job Costing displays an error message.
You will not be able to save options in the Options screen until all other users have left Project and Job Costing and all other Project and Job Costing screens are closed.
Single-User Processes
If you are posting transactions from any screen, you will lock all other users out of the group.
For example, while you are running Post Billing Worksheets, a second user, who wishes to use Post Transactions, will have to wait until the program has finished posting worksheets.
When you run a single-user process, other users can work in screens not included in the group, but if they are updating records for transactions referenced by the process you are running, they may be unable to save their work. Once again, make sure no one is working with the transactions you are trying to post.
Multiuser Processes
Apart from the PJC Options screen and transaction posting, all other processes and functions in Project and Job Costing feature multiuser data protection.
To allow efficient data entry, Project and Job Costing does not lock records. Instead, it uses audit stamps to prevent two workstations from making changes to the same record at the same time.
In a network environment, audit stamps protect data integrity. The system will only save changes to a record if the current audit stamp for the record is the same as the audit stamp when the record was read. For example, if two users are editing the same batch, the first one to press the Save button will succeed in updating the file. The second user will get an error message when attempting to save and will have to re-do their work in that batch.