Scripting

I avoid using the VBScript SendKeys method whenever possible, but sometimes it is the only solution. I have a situation where I am using it to invoke the Accept button (I cannot use the BOI InvokeButton method since this script has to run on a MAS 200 Client in a button script where BOI is not available). The SendKeys method works flawlessly, but only about 50% of the time. It is a simple script and I've traced it to KNOW that the statement is being executed, but the Accept button sometimes doesn't invoke. Idea?

I've often had to put in a sleep before invoking a sendkeys to give the system time to catch up to the keystrokes, and yes unfortunately it is often our only option :(

Thanks Barbara, but the Sleep method isn't available in the environment of a button script. I tried a spin loop, but that didn't work either. I'm thinking the days of .sendkeys are over. At least for MAS 200.

I call a script from a script or something like that, it's been a little while since I've done it. It's not available in the script on the button itself, but it will be available to the called script (I shell a vbs script if I recall correctly and do the processing in there). It's hokey but it works.

That's my experience also, but my issue does't work any better in a called script using Sleep.

weird, I've always gotten something like this to work: wscript.sleep(1000) Sorry I wish I had a solution for you.

Did you ever get this resolved?

I solved the problem by seperating the function into two buttons. One runs on the server and the other runs on the client. This actually turned out to be a boon for the flexibility of this particular application. It is for printing lables to a locally attached thermal printer. Seperating the buttons allow user's that don't have a thermal printer to queue labels that can be printed by the workstation that does.