Field advance after lookup

[Cheryl Lemire]

Re: Field advance after lookup

Chet,

You really are not being very clear with your exact situation, which is why we are all running around in circles here. You say:

I'm using a lookup scenario exactly like the customer lookup in AlphaSports Invoice form.

This can't be true because you mention that we need to remove the autopopup in the field rules in Alphasports. If you were using the exact scenario, the OnChange event would work. You also mentioned in another post something about a custom browse for the lookup. Then you say something about scanning. These are all different things.

Posting my database up here is not an option.

I don't know about others, but I do not have the time to continue 'guessing' at what your exact scenario is. You really need to take the time to post your database here. I do not understand why this is not an option.

All you have to do is take the table/set that the form in question is based on (and your custom lookup browse that sounds like you are using), copy them to another directory, remove the data that is in those tables if it is sensitive data and add a few sample records. Then let us know the exact steps we need to take, what the results are, and what results you desire.

If you cannot take the time to do those simple steps, I do not see how you can expect us to take the time to assist you. We are spinning our wheels trying to find a resolution for you without all of the information.

You also mention scanning a product. I am not certain at this point if you are trying to move to the next field during a customer lookup or during the scanning of the product. These are two completely different issues and would be addressed in different manners.

[Mike Wilson]

Re: Field advance after lookup

Chet and all,

I am seeing the same thing Chet is seeing with Gabriels example because all the field values for the Item field have the same value = item #. The system is not sensing any change. Chet, if you change the values in the Test table so the fields have different values, the action you desire will happen.

Additionally I have added for you a different alternative that I like to use for lookup, which is a List-List dialog box. I place the script in the Layout field OnArrive event. An Xdialog box gives far greater flexibility for the user to customize the lookup, and followed with the action <Fieild>.activate() or anything else

[Mike Wilson]

Re: Field advance after lookup

oops,

[G Gabriel]

Re: Field advance after lookup

Chet:
I tried the same code with what you refer to as "custom" browse, it works!
Maybe there are other interfering elements in your DB. If you can, post it for others to review.

[Chet Sapino]

Re: Field advance after lookup

Chet,

You really are not being very clear with your exact situation, which is why we are all running around in circles here. You say:



This can't be true because you mention that we need to remove the autopopup in the field rules in Alphasports. If you were using the exact scenario, the OnChange event would work. You also mentioned in another post something about a custom browse for the lookup. Then you say something about scanning. These are all different things.



I don't know about others, but I do not have the time to continue 'guessing' at what your exact scenario is. You really need to take the time to post your database here. I do not understand why this is not an option.

All you have to do is take the table/set that the form in question is based on (and your custom lookup browse that sounds like you are using), copy them to another directory, remove the data that is in those tables if it is sensitive data and add a few sample records. Then let us know the exact steps we need to take, what the results are, and what results you desire.

If you cannot take the time to do those simple steps, I do not see how you can expect us to take the time to assist you. We are spinning our wheels trying to find a resolution for you without all of the information.

You also mention scanning a product. I am not certain at this point if you are trying to move to the next field during a customer lookup or during the scanning of the product. These are two completely different issues and would be addressed in different manners.

[Chet Sapino]

Re: Field advance after lookup

Chet,

You really are not being very clear with your exact situation, which is why we are all running around in circles here. You say:



This can't be true because you mention that we need to remove the autopopup in the field rules in Alphasports. If you were using the exact scenario, the OnChange event would work. You also mentioned in another post something about a custom browse for the lookup. Then you say something about scanning. These are all different things.



I don't know about others, but I do not have the time to continue 'guessing' at what your exact scenario is. You really need to take the time to post your database here. I do not understand why this is not an option.

All you have to do is take the table/set that the form in question is based on (and your custom lookup browse that sounds like you are using), copy them to another directory, remove the data that is in those tables if it is sensitive data and add a few sample records. Then let us know the exact steps we need to take, what the results are, and what results you desire.

If you cannot take the time to do those simple steps, I do not see how you can expect us to take the time to assist you. We are spinning our wheels trying to find a resolution for you without all of the information.

You also mention scanning a product. I am not certain at this point if you are trying to move to the next field during a customer lookup or during the scanning of the product. These are two completely different issues and would be addressed in different manners.

Cheryl:

Ok I apologize for not being exact or appearing to be inexact. This is what I want to do and cannot figure out how to do it.

I probably should have done this from the beginning as it would have saved us all a lot of trouble.

1. Open up Alphasports
2. Edit the field rule for the Invoice Header table and set Auto Popup to "Do Not automatically popup" and set Allow Exceptions to "Popup on Mismatch"
3. Open up the Invoice Form in design mode and set the tabs so that the first tab field is customer_Id and the second tab field is Date. For this example, I don't care how the rest of the tabs are set.
4. Run the form and select a customer by pressing the "Blue" lookup button in the customer ID field.
5. A browse dialog list appears. Select a customer. The Browse list closes and the cursor is sitting on the Customer ID field. I don't want this to happen. I want the focus to move to the Date field after I select the customer rather than remain on customer ID, i.e.

Code somewhere in some event, field rule, etc.
.....
date.activate()

Instead of pressing the Tab Key to move from customerID to Date when it loads with the selection, I want the move/activate() to be automatic to save the Tab keystroke.

I hope this is clear.

I need to find a solution to this. This normal behavior of having to tab off a lookup field after doing the lookup is "precambrian."

As I said earlier, I can do this in under 20 seconds with Clarion For Windows with no code.

This capability should be in A5 after seven versions.

[Cheryl Lemire]

Re: Field advance after lookup

Chet,

I attempted to follow your steps. In step 4 you say 'the "Blue" lookup button', all I see is a drop down arrow, no blue button. So I selected the drop down arrow and the customer list opens. I double click on a customer and the dialog closes and brings me back to the customer id field as it should.

If you open the invoice form in design mode, right click on the customer id field, select events, OnChange, xbasic code:

parentform:date.activate()

Save your form and select the customer again, you will be brought to the date field as expected. This is what I and others have suggested to you throughout this thread.

[Tom Cone Jr]

Re: Field advance after lookup

Chet, bad news. Using my XP (sp2) machine and following your steps focus moves to the Date field automatically. It does not return to the Customer_id field after I select the id from the lookup dialog.

Date.activate()

in the OnChange event for the Customer_id field did the trick, whether the lookup pops up or pops down.

BTW, you should use the popup if the user is permitted to "add records" to the lookup list, cause that option doesn't work on the popup down.

-- tom

[G Gabriel]

Re: Field advance after lookup

Chet picked up a bad time for his thread. I was responding to Cheryl's thread and his at the same time using the same test table. In the test table, the field "item" shows one value only: "Record #", which was meant for cheryl's. All you have to do is enter a number of different values and you will see multiple choices.

To clarify some gibberish:

a-YOU CAN NOT PROGRAM A DEFAULT BROWSE OR FORM. Once you open a default browse/form in design mode and make any changes to it and if you want to save it, then you have to give it a name and from that point on it is no longer a default browse or form. SO, DO NOT EXPECT TO SEE ANY CODES, ANY EVENTS, ANY SCRIPTS..ETC IN A DEFAULT BROWSE OR FORM.

b-Chet refers to a "Custom " Lookup browse. I am not sure what that is. I think he is referring to the fact that alpha gives you the option to use the default browse, or any other browse that you might have created, as the lookup browse. In the end, any one you use, makes no difference and has no effect on the OnChange event.

c-The OnChange event fires anytime the field's value changes. Don't let the term confuse you: you might the take the name to mean:
the event will only fire when you put the object in "change" mode only. WRONG.
or, the event will only fire if you already have a value in a field and you "changed" that value. Wrong again.

The event will fire whether you already have a value in the field and changed it (put the object in "change" mode) AND will also fire if you put the object in "enter" mode i.e entering a new record. In essence, when you enter a new value in a field in a new record, you are changing the field's value from null to something.

The attached zip file shows:
1-The event will fire when you change the value
2-Will fire when you add a new record
3-Will fire with the lookup using a browse named "test", not the default browse.

Go to the form "Test_chet"
The zip file has other irrelevant objects, please disregard.

I don't know what else is there to say about this issue.