So I have a table that has a field (N,3,0).
In the fieldrules, this field has a lookup designed, that offers choice from another table using a linking field and a filter on the external table to get the right records. The filter is matching a field from the lookup table to the contents of a variable set before entering the form where the field rule executes.
The lookup is displayed as a drop-down list box, forcing closest match and popping up on entrance. There is a specific browse designed for the lookup.
No error messages appear upon designing the field rule. Everything seems to be OK there.
Note: I used exactly the same system in a v9 application and it worked (and still works under v9) as a charm. Actually, I just added the table including the field rules from this specific v9 application (copy, paste, adding table) and although it worked without error in v9, under v11 it produces an error message on execution.
What happens?
I start with a lookup table that has records, but the field that gets looked up has a value of 0. So, not "empty" but 0,00.
I open the form on my table, and when I reach the field concerned it opens the dedicated lookup browse, and is showing the available records. No probs till here. Then, I click on the desired record, and next it fills the fields of the form table (as far as I can see nothing is going wrong actually!) BUT it produces at the same time an info dialog box saying:
ERROR
i
"Call was canceled"
OK
So, brothers in arms, what the hack is that?
It does not seem to have any strange consequence besides showing the error box.... values are entered correctly by the lookup as it seems. Nothing is left out or discarded as far as I can see. The value 0,00 is nicely put in the right field as shown on the form.
So, why the strange info box??
Clicking OK allows me to go on, without any problem shown.
This also happens in a second field rule table lookup I defined, but there the field that I looked up had not the value of 0,00 but an actual value. So this seems not to be the problem. However, the same info box appears. And again, normal import of the value without any visual residing problems.....
The strange thing is, that when I enter the SECOND record in the table that uses the field rule lookup, this behavior is NOT duplicated....
So it only happens with the first record that I put in the table. Why??
When I manually check the value of all fields later by opening the tables, I can find no value problem and everything looks ok.
I have tried this various times, and the problem gets duplicated any time.
Who can help me out with this? I don't want an error box displayed to the customer when there is nothing actually wrong of course.
What changed in v11 to make this box appear now, where it does not under v9 ?
How to get rid of it?
Thanks in advance for any of your help!
In the fieldrules, this field has a lookup designed, that offers choice from another table using a linking field and a filter on the external table to get the right records. The filter is matching a field from the lookup table to the contents of a variable set before entering the form where the field rule executes.
The lookup is displayed as a drop-down list box, forcing closest match and popping up on entrance. There is a specific browse designed for the lookup.
No error messages appear upon designing the field rule. Everything seems to be OK there.
Note: I used exactly the same system in a v9 application and it worked (and still works under v9) as a charm. Actually, I just added the table including the field rules from this specific v9 application (copy, paste, adding table) and although it worked without error in v9, under v11 it produces an error message on execution.
What happens?
I start with a lookup table that has records, but the field that gets looked up has a value of 0. So, not "empty" but 0,00.
I open the form on my table, and when I reach the field concerned it opens the dedicated lookup browse, and is showing the available records. No probs till here. Then, I click on the desired record, and next it fills the fields of the form table (as far as I can see nothing is going wrong actually!) BUT it produces at the same time an info dialog box saying:
ERROR
i
"Call was canceled"
OK
So, brothers in arms, what the hack is that?
It does not seem to have any strange consequence besides showing the error box.... values are entered correctly by the lookup as it seems. Nothing is left out or discarded as far as I can see. The value 0,00 is nicely put in the right field as shown on the form.
So, why the strange info box??
Clicking OK allows me to go on, without any problem shown.
This also happens in a second field rule table lookup I defined, but there the field that I looked up had not the value of 0,00 but an actual value. So this seems not to be the problem. However, the same info box appears. And again, normal import of the value without any visual residing problems.....
The strange thing is, that when I enter the SECOND record in the table that uses the field rule lookup, this behavior is NOT duplicated....
So it only happens with the first record that I put in the table. Why??
When I manually check the value of all fields later by opening the tables, I can find no value problem and everything looks ok.
I have tried this various times, and the problem gets duplicated any time.
Who can help me out with this? I don't want an error box displayed to the customer when there is nothing actually wrong of course.
What changed in v11 to make this box appear now, where it does not under v9 ?
How to get rid of it?
Thanks in advance for any of your help!
Comment