Work period open and closing issues across terminals

Version 4
1

Hi
We have run into this issue a few times and we are looking for a solution. We have one main terminal as server and a another in the office which is used by the manager during closedown And reporting. Some times they will open the work period on one terminal and close on another or vice Versa. Opening a work period doesn’t seem to always work across the terminals.

Yesterday we opened a work period on the server where all the orders were entered and closed it on the office terminal. The period showed as still open on the main server which was then used to enter new bills. When it came to close the end work period button was pressed on the server and it showed the end of the period as the time it was original closed on the office terminal. This meant that no work period report was available for any of the items entered during this ‘phantom’ period. However th bills are still showing on the ticket screen?

So effectively we have bills unassociated with a work period. Is there anyway to get them back onto a work period so they can be included in reporting?

2

Do you have message server running correctly??

3

How do you mean showed as still open?

4

So on the computer which has not had the work period closed. The period shows as still open and you are able to use the pos screen to enter bills.

We have our message server up and running without hitch,

When you close or open a work period on one server or terminal, should it not close that period across all other connected terminals?

5

With version 4 you have to shutdown terminals then close work period. Version5 has better control of this and it won’t allow that.

So your options are shutdown terminals before close work period or upgrade to version 5 for better control.

6

They are defiantly linked to same DB right?

7

JTRTech from his explanation it sounds like he has it setup properly its more of how v4 works vs v5. With v4 you have to log out of all terminals before close of work period otherwise it will allow you to create tickets etc. V5 has better control over this and will not allow that. I recommend upgrading to v5.

Or you can continue to use v4 but understand that terminals need to be logged off before close of work period.

8

I never experienced that, but think I implemented a work period program setting to work with my switch user config which I guess fixed the issue.

9

Ok so no easy solution for this, we are planning an upgrade to v5 in the next week so hopefully that fix everything. Thanks Guys!

10

The easy solution is to just log out of all terminals before close. That’s fairly simple. Or you can upgrade to v5.