I have seen the code and I use something very similar in this application to keep the capslock and numlock keys on for my users because the VB sendkeys command has a nice little bug that toggles the numlock and or capslock keys when used.
The problem with using the capslock key is that I believe that VB SendKeys operates independently of the capslock key state. In other words, if I stuff a variable with a caps string, then SendKeys should send that capitalized string to the target regardless. -----Original Message----- From: Lew Hundley [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2003 4:45 PM To: [EMAIL PROTECTED] Subject: RE: [Talk] Anyone have any ideas about this? Daron, I don't know the cause, but I think I might have a solution for you. I have an interface that the user has to enter Meditech data in CAPS and WinStrat (the interfaced application) in lower case. With Rich's help (ok, I just presented the problem, and he supplied tools, and I refined and tested the code) I implemented functionality that can check the CAP LOCK key and turn it on or off as desired. You might want to try using this code to turn off the CAP LOCK key, and see if it helps. The code is in the User submitted scripts at www.bossoft.com. Just to back up that the caps key might be on, when your Windows application has focus, is the CAPS LOCK light on on your keyboard? Good Luck. Hope this helps, Lew Hundley Information Specialist - Programmer Silverton Hospital Silverton Oregon 503.873.1657 [EMAIL PROTECTED] -----Original Message----- From: JOHNSTON,DARON P [mailto:[EMAIL PROTECTED] 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.
