Sage 100

Client's PCI level is 1, SAQ C. (whatever, I am so glad I don't have to figure all that out!). So without going into lengthy details about their internal controls; they are hoping to find a way to NOT allow certain users to log into Sage from certain PC's. So user A can log into Sage on computer 1, but not computer 2. Is there a way to do this? maybe via scripting? @Sage100AdvancedScripting

This wouldn't restrict by computer but as you likely know, if you turn on Unified Logon in System Config you can then go to User Maintenance to set up a User Logon = Windows Logon for every single Sage 100 user. This means on startup ever single user will automatically be logged into Sage with their User ID. They will never see a User/Pswd prompt (unless an override flag is added to SOTA.INI ) and File / Change User will not allow them to switch users. A Microsoft security concept from awhile back. Otherwise to do it the way you've described, one of the Sage start-up programs needs to be modified or overridden so it would check a user-computer table and show the No Go message. Other considerations too such as Standard vs Classic Launcher. I can give you more details if you want to PM or email me.

Thanks @AlnoorCassim , they don't like the idea of Unified Login. I am actually playing with UI scripts right now and the oSession.WorkstationName property to maybe just hide the credit card tab in Sales Order and AR Invoice data Entry. I think this would provide the solution they are looking for as well. If I add it on Panel PostLoad, and have it validate against a UDT where there are ""allowed"" workstation names. Thoughts?

Oh I thought you needed to enforce on start-up. Yes your idea should work swimmingly. I think you can disable but not hide it. But try it anyway: oUIObj.SetFolderState(""PCreditCard,PCreditCardW"", ""DISABLE"") or the ole oScript.SetUIControl(""fldr.PCreditCard"", ""DISABLE"") oScript.SetUIControl(""fldr.PCreditCardW"", ""DISABLE"") PostRead might a better place but give it a whirl and see what works best.

Great! Thanks @AlnoorCassim that sends me in the right direction :)