In theory in cases like this where table is open on two terminals I believe the expected behavior should be the changes made by the first user to logout are saved and the second user gets a message saying something like the ticket has been altered elsewhere. Although am not sure off the top of my head if the seconds users orders are canceled or samba does its best to merge their changes too.
@rightguys This is an already fixed issue but seems like you found a case that reproduces it. That relates with some performance optimizations so I’ve secured it not to happen again. That will work fine on next (.49) update.
That reference was to preventing duplicate discounts, doesn’t prevent a ticket being opened at two terminals at the same time.
Now I am more familiar with ticket/entity states I will probably try and work in a ‘Active Ticket’ state rather than using program settings.
Emre said he knew what the issue was and was related to some other updated he made and has corrected the issue in .49
If you want to show your close ticket rules can try and see if any issues with it but emre seems to know what the issue is from the crash report, and if it was a rule issue he would have said.
Wait, so you’re saying that I don’t have to RDP into my server computer. The Computer #2 can have SambaPOS 5 installed locally and it will share information with Computer #1?
I’m still very new to SQL Express.
Personally, have done about 25 samba installs with about 50 terminals, from singles to 4 terminals.
I have never used more than a core2duo won 7 pro pc 4gb ram with that machine being one of the 4 terminals and never had any issues.
You probably could have got away with not having server windows yes but heinsight is fabulous thing
Windows server is overkill for a small setup.
If I was doing more than 6-7 terminals I might consider it but more likely just use a more powerful machine and have it dedicated rather than doubling as a terminal .
You will get better performance from SQL Express. No technically you did not need to do that but if you already have it then you could benefit from better performance. There is no need to run RDP unless you plan to use non windows tablets. Non windows tablets are typically more expensive for what you get. Additionally if you run rdp you have to purchase more licenses for RDP Machines. This means more cost. Its better to just get a high performance network setup and use local installs connected to the SQL Server