Can I add "10% discount" and "20% discount" buttons to POS screen?
How can I do that?
Thanks a lot!
Can I add "10% discount" and "20% discount" buttons to POS screen?
How can I do that?
Thanks a lot!
Use a macro and download everything in the AltKeys directory of this page:
HTH, Tom
What are those files used for? Which folder should I save the files?
I guess the altkey files are used for the POS custom button. Please follow instructions in the readme.txt.
For me ,the problem is I can't record the macro of discount at all. The following are the process of recording.But when I press Alt+F1 nothing happens. ctrl+F3 to start recording choose the button Alt+F1 and caption is "10% discount) Shit+F3 (Then the red recording icon stops flashing and a pause icon is shown on it) choose "Discount from retail price" by the tab key input the percent "10%" press "Enter" choose the reason code and press Enter ctrl+F3 to stop recording
Is this because of that pause sign in the red record icon? What can I do with it?
There's no hard limit on the number of buttons you can create. There is a practical limit on how many can display - if you create more buttons than fit vertically on the transaction screen at normal size, they will resize to display all of the buttons. Eventually, they will shrink to the size where the caption or graphic becomes unreadable...
Glenn Adams Tiber Creek C> OK, I figured out the alt keys file, I didn't understand at first that you
Craig,
The only file you need is testdll.dll - the remainder are the source code (I didn't write it). On second thought, you'll need the readme.txt file, too.
Download and read the readme.txt file. It's probably best to read it more than once.
Download the dll, save it in the store ops directory. Register the dll per the instructions in the readme file. Record your macro. Create your Custom Button - assign it to the appropriate altkey (again, see the readme). The Custom Button Style = COM Object (Session Object) and Command = testdll.AltFx
If you're still having trouble, let me know.
I have used it for both complex and simple macros. Some, IMO, I should not have had to create. For example, there should be a FireEvent for 'Make Payment' but there's not, so I used a macro.
Tom
"Craig" wrote:
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.