Some more ideas: 1. Switch to a Windows Connection...this may only require changing the Activate to a Connect and the SendKeys to a Key. Sometimes it's more complex but perhaps not here.
2. Just to be sure...this is Meditech Magic isn't it? If it's Client Server, there's some Capslock activity associated with its keyboard in Boston WorkStation which might be a factor. Rich McNeil Boston Software Systems 866 653 5105 www.bostonworkstation.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of JOHNSTON,DARON P Sent: Tuesday, September 16, 2003 10:33 AM To: '[EMAIL PROTECTED]' Subject: RE: [Talk] Anyone have any ideas about this? Hi Rich, Ok, here it is. I ran a very simple VB app that takes a mixed case string variable, activates notepad, then uses sendkeys to send it over. The results, usually the CapsLock state DOES make a difference. If capslock is off, the text is entered correctly. If capslock is on, all characters in the string are entered in reverse case. I did notice, however, that a couple of times when I ran this code, everything worked perfectly. The few times that all worked well, I noticed that the CapsLock key flashed for a second which leads me to believe that SendKeys actually turns CapsLock off to send the keys and then turns it back on (if it was on before). When the app is malfunctioning, the capslock key does not flash when sendkeys is executed. If this is, in fact, how sendkeys works, it doesn't seem like a very reliable method to me and is probably the root of the other NumLock/CapsLock problems that have been around for so long. Next I tried the Key command using the windows connection instead of activate. Seems to work fine. Text is entered as expected and no crazy flasing of the keyboard lights. Thanks, Daron -----Original Message----- From: Rich McNeil [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 16, 2003 7:50 AM To: [EMAIL PROTECTED] Subject: RE: [Talk] Anyone have any ideas about this? This seems serious...I setting up an environment here, and I hope I'll see the problem. Daron, would you verify that this is happening in a very, very simple script? Also, in this simple script, try the Key Command in Boston WorkStation's Windows Connection. It's functionally similar to SendKeys but is separately built from the ground up. Again, if I can see the problem here, I should be able to do something about it. Rich McNeil Boston Software Systems 866 653 5105 www.bostonworkstation.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of JOHNSTON,DARON P Sent: Monday, September 15, 2003 11:25 PM To: '[EMAIL PROTECTED]' Subject: RE: [Talk] Anyone have any ideas about this? I am currently using LCASE as a temporary solution. I am converting the Capitalized data from Meditech to lower case in code before I use SendKeys to send it to the target (which converts it all back to upper case). Again, this is just a temporary solution and I really hate temporary solutions :) Daron -----Original Message----- From: Paul Donoughe [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2003 4:51 PM To: [EMAIL PROTECTED] Subject: RE: [Talk] Anyone have any ideas about this? If Lew's idea doesn't do it for you, and you want to ensure that the values are either in upper or lower case, give these commands a go. Ucase( your value ) will make what ever it receives upper case. Lcase( your value ) will make what ever it receives lower case. Paul -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of JOHNSTON,DARON P Sent: Monday, September 15, 2003 2:31 PM To: [EMAIL PROTECTED] Subject: [Talk] Anyone have any ideas about this? I have a small application that scrapes 5 fields from Meditech and enters them into a Windows screen. Very simply, I activate the Meditech windows, grab the data, activate the windows screen and dump it in using Sendkeys, see code below. All data in Meditech is in upper case. However, as of this morning, the sendkeys dumps the data in lower case. (Actually the opposite case). If the VendorName was "XYZ Corp" in Meditech, it would end up "xyz cORP". I have thrown all the variables into a message box one line before the SendKeys to prove to myself that SendKeys was sending the correct case. The 5 PCs (Windows 2000) that are running this app were updated to service pack 4 over the weekend and also had a Microsoft Security Patch installed (KB824146). They have been working fine for months but now, all 5 are experiencing this problem. I have installed SP4 and the security patch to 3 other PCs in an attempt to recreate the problem but all other PCs function normally. There has got to be something simple that I am missing. Any ideas? Thanks, Daron Activate "*.MIS*" 'Activates the Meditech window so we can grab the data Wait 0.5 VendorNo = Trim(View(Row:=3, col:=8, length:=11)) VendorName = Trim(View(Row:=3, col:=20, length:=25)) InvoiceNo = Trim(View(Row:=6, col:=1, length:=15)) PONumber = Trim(View(Row:=9, col:=21, length:=12)) TxnDate = View(Row:=9, col:=10, length:=8) Activate "*Ascent Capture*" 'Activates the Ascent Capture window so we can enter the data Wait 0.5 SendKeys VendorNo & "{TAB}" & VendorName & "{TAB}" & InvoiceNo & "{TAB}" & PONumber & "{TAB}" & TxnDate & "{TAB}", True frmMain.LCommand.Caption = "Waiting..." Daron Johnston Application Programmer Woman's Hospital 225.924.8543 [EMAIL PROTECTED] This e-mail may contain confidential information which is intended only for the use of person(s) named above. If you are not the intended recipient, you are hereby advised that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is prohibited. If you have received this transmission in error, please notify the sender and delete this e-mail from your computer.
