I have learned a little more but I am not done testing. Based on the part number someone is looking up, if the lookup code does not encounter a "PAUSE 2 USING variable" or a "CHOOSE variable FROM table", then it works as expected with the variable selected and the cursor blinking. If I comment out the pause or choose the form works as expected.
In the past, I have tried to figure this one out several times, but dropped it due to it's not that big of a deal and more pressing issues come up. But it would be nice to finally figure this one out, because I know it should work.
Kenny Camp
----- Original Message ----- From: "Javier Valencia" <[EMAIL PROTECTED]>
To: "RBG7-L Mailing List" <[email protected]>
Sent: Monday, May 09, 2005 6:41 PM
Subject: [RBG7-L] - Re: Losing the blinking cursor or autoselect on a form called from a form
Kenny: I normally set my regions so the selected row is highlighted (Scrolling Region Properties>Selected Row) on a different color than the background, this way it is easy to see what row has focus...you probably have already done this but I thought I would bring it up just in case... Javier,
Javier Valencia, PE
President
Valencia Technology Group, L.L.C.
14315 S. Twilight Ln, Suite #14
Olathe, Kansas 66062-4578
Office (913)829-0888
Fax (913)649-2904
Cell (913)915-3137
================================================
Attention:
The information contained in this message and or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact the sender and
delete the material from all system and destroy all copies.
======================================================
-----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of Kenny Camp Sent: Monday, May 09, 2005 6:31 PM To: RBG7-L Mailing List Subject: [RBG7-L] - Re: Losing the blinking cursor or autoselect on a form called from a form
Thanks for the input, Javier. I agree with you and use REFRESH and
SET_FOCUS a lot with great success on other forms including the Sales order
form that calls this lookup form.
I think the next step is to start commenting out blocks of code to simplify
the process, and see if the cursor re-appears.
To restate the problem, the focus is on the correct field, and the form
works exactly as intended, users just can't see focus anywhere on the form.
Kenny
----- Original Message ----- From: "Javier Valencia" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Monday, May 09, 2005 6:04 PM Subject: [RBG7-L] - Re: Losing the blinking cursor or autoselect on a form called from a form
Kenny: I have had good luck using the PROPERTY TABLE table_name 'REFRESH' and SET_FOCUS commands; in fact, I have replaced all the places where I had NEXTROW, PREVROW with this construct with good results. One thing that you need to be careful when using the NEXTROW, PREVROW approach is that if you are in the last row of region the focus will end up in the previous row; likewise, if you use PREVROW, NEXTROW and you are on the first row the focus will end up in the second row...a minor of major annoyance depending on your perspective... Javier,
Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln, Suite #14 Olathe, Kansas 66062-4578 Office (913)829-0888 Fax (913)649-2904 Cell (913)915-3137 ================================================ Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all system and destroy all copies. ======================================================
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] Behalf Of Kenny Camp
Sent: Monday, May 09, 2005 5:48 PM
To: RBG7-L Mailing List
Subject: [RBG7-L] - Re: Losing the blinking cursor or autoselect on a form
called from a form
Albert,
Yes, I have tried REFRESH, and POST, and combinations of skip to another
field and back and set_focus to another field and back and everything else
I
can think of. They are still commented out in my code.
The ON AFTER START runs before the lookup code but I have tried SET_FOCUS
there and in several other places in the code hoping to solve this anomaly
but no success. The lookup code includes several possible CHOOSE stamens
that are usually escaped and PAUSE statements that can be triggered but
they
don't seem to affect the behavior.
This lookup form is a form based on the dummy table concept with one row of data, but I will add a second row and try the NEXT PREVIOUS idea. Thanks a lot. I'll try anything and I had not thought of that one.
The form ( and focus) works perfectly as it is normally called, independently from the sales order form, and is used thousands of times a day. Only when I call it from the sales order form, with the not null variable triggering the lookup code, do I see this behavior.
Thanks for the input.
Kenny Camp
----- Original Message -----
From: "Albert Berry" <[EMAIL PROTECTED]>
To: "RBG7-L Mailing List" <[email protected]>
Sent: Monday, May 09, 2005 5:27 PM
Subject: [RBG7-L] - Re: Losing the blinking cursor or autoselect on a form
called from a form
In the ON AFTER START eep, try this: PROPERTY TABLE <FormTableName> 'REFRESH' just before the SET_FOCUS One would not think you would need it, but ...
If that doesn't work, in the ON AFTER START eep NEXTROW PREVROW just before the set_focus.
And if that doesn't work, try the NEXTROW; PREVROW just AFTER the set_focus.
And if that doesn't work, try a case of Heineken's.
--- Kenny Camp <[EMAIL PROTECTED]> wrote:version 7.1 build 78, 79, 80 or 81
I am calling an inventory lookup form from a sales order entry form's
scrolling region and carrying the existing part number variable into the
inventory lookup form which automatically looks up the pertinent
information
for that part.
Everything works perfect except the blinking cursor is missing and the variable is not shown in inverse color like it should. The part number variable must be currently selected, because a space or a backspace, or typing any character will delete the entire number.
Pressing ENTER or clicking any of the buttons on the form forces a fresh
lookup and the cursor and selected part number show correctly on the
form.
We can currently work around it by clicking on one of the read only variable edit fields and then clicking back to the part number variable edit field, and the cursor appears. Or just training the users to expect this behavior, but...
I'd love to perfect this routine. Any ideas?
Kenny Camp IT Manager Electro Enterprises Oklahoma City, OK
Albert Berry Management Consultant RR2 - 1252 Ponderosa Drive Sparwood BC, V0B 2G2 Canada (250) 425-5806 (250) 425-7259 (708) 575-3952 (fax) [EMAIL PROTECTED]
