I have a smal problem.
I have a simple table with 2 field: ID, field1
ID is autonumbering
Field1 is a VARCHAR field containing small data used in a LOOKUP.
1 = E1
2 = NO
3 = 2
So far so good.
But when displaying this data in a Calendar the lookup not shown correctly with the value 'looking' like an INTEGER. So in this case ID 3 is show an incorrect value (in my project the first value with alfabetic characters). When the idexes 1,2 are use to look up a value, the lookup is correct.
So SC9 is treating the '2' value of the field as an INTEGER. When i put a underscore before the '2' and making the fieldvalue '_2' (so a STRING!) everything works fine.
So the problem is the fact that SC treats this value as a INTEGER.
Even more weird is the fact that in all other apps the problem does not appear. So in FORMS/GRIDS the lookup is correct even with the '2' value.
Im using mysql
So i tried using CASE to define the type of value = not working.
Any suggestion? or is this a BUG?
I have a simple table with 2 field: ID, field1
ID is autonumbering
Field1 is a VARCHAR field containing small data used in a LOOKUP.
1 = E1
2 = NO
3 = 2
So far so good.
But when displaying this data in a Calendar the lookup not shown correctly with the value 'looking' like an INTEGER. So in this case ID 3 is show an incorrect value (in my project the first value with alfabetic characters). When the idexes 1,2 are use to look up a value, the lookup is correct.
So SC9 is treating the '2' value of the field as an INTEGER. When i put a underscore before the '2' and making the fieldvalue '_2' (so a STRING!) everything works fine.
So the problem is the fact that SC treats this value as a INTEGER.
Even more weird is the fact that in all other apps the problem does not appear. So in FORMS/GRIDS the lookup is correct even with the '2' value.
Im using mysql
So i tried using CASE to define the type of value = not working.
Any suggestion? or is this a BUG?
Comment