Been discussed before but I cant see a resolution to this question?
I need a valuelist with a custom list of integers - 1 thru 50. The dataprovider is INTEGER, and based on a combobox, and I can build the valuelist with these entries. However - when the form is saved I get:
Valuelist: vlt_setyears2 used with different types
The valuelist was already created for type: TEXT for the dataproviders: fc_lib_set_year_to
So it can’t be uses also for type: INTEGER for the dataprovider: fc_lib_set_year_to
Please check these dataproviders of this valuelist: vlt_setyears2
Q. How can I enter these values and have the valuelist seen as built for integer not text?
That warning is an indication that you have that value list assigned to a string data type field somewhere already. You have to use separate value lists for different data types even if the value list values are the same.
david:
That warning is an indication that you have that value list assigned to a string data type field somewhere already. You have to use separate value lists for different data types even if the value list values are the same.
That’s the problem David - this is a brandy new valuelist - and I’ve tried creating them over again (new name - even restart developer before making a new one)!
Seems regardless what I do when I create a new valuelist its the wrong type!
david:
Ah yea, go to the debug perspective and kill the client thread once this starts happening to get things to reset.
As I said David - even restarting Developer doesn’t help.
I have got a valuelist working on this dataprovider by starting a new valuelist, creating it against the dataprovider as DataBase Values (as opposed to custom) then after saving it - editing it to take a custom listing of integers.
I have this message from time to time, but I can’t remember how it dissapeared and why
I have the feeling it’s a but but I am not sure.
Regards, Robert
Kahuna:
david:
Ah yea, go to the debug perspective and kill the client thread once this starts happening to get things to reset.
As I said David - even restarting Developer doesn’t help.
I have got a valuelist working on this dataprovider by starting a new valuelist, creating it against the dataprovider as DataBase Values (as opposed to custom) then after saving it - editing it to take a custom listing of integers.
Johann, the problem is that this occurs only seldom, I assume under certain circumstances, because, as you demonstrated, we would never be able to attach a value list to a field, but of course we can do that. But in rare conditions, I also got the same error message as Ian described, but, as said, I don’t know under what circumstances this happens.
Best regards, Robert
jcompagner:
i cant reproduce this
i create a valuelist call it “integers”
on the custom values i type
1
2
3
4
5
then save it
go to a form get a integer column text field and attach the valuelist integers
start the client and the field shows 1-5 in the list.
Robert Huber:
Johann, the problem is that this occurs only seldom, I assume under certain circumstances, because, as you demonstrated, we would never be able to attach a value list to a field, but of course we can do that. But in rare conditions, I also got the same error message as Ian described, but, as said, I don’t know under what circumstances this happens.
Agreed, except that I am almost certain it only happens to me because:
1- client thread is running during the whole time I’ve been messing around with value lists;
2- the value list in question is still lurking somewhere sinister…attached to a field of the wrong data type on a form I thought I had deleted…
But this might be just my imaginations. Because every time I get to the point when I’m sure it has to be Servoy’s fault, the problem goes away. Poof.
Moral of the story: blame it on Servoy and the problem goes away. But only if you have the mind reading version of Servoy that I always seem to accidently download.
david:
[
Agreed, except that I am almost certain it only happens to me because:
1- client thread is running during the whole time I’ve been messing around with value lists;
2- the value list in question is still lurking somewhere sinister…attached to a field of the wrong data type on a form I thought I had deleted…
But this might be just my imaginations. Because every time I get to the point when I’m sure it has to be Servoy’s fault, the problem goes away. Poof.
Moral of the story: blame it on Servoy and the problem goes away. But only if you have the mind reading version of Servoy that I always seem to accidently download.
David - for me there was no trail of the original valuelist left in memory - proved in two ways:
Restart Developer (and in one instance reboot of PC)
Brand new valuelist started.
Also this was tried with a client running and without. However like it did for you, it magically disappeared - after creating a new valuelist using database values, then converting to custom.
in the developer if you just go to the debug smart client and close the solution (it will reload it again)
then everything should be in an original state. If that is not the case then we have a bug.
jcompagner:
in the developer if you just go to the debug smart client and close the solution (it will reload it again)
then everything should be in an original state. If that is not the case then we have a bug.
I just tried this. in the example above, integers valuelist attached to an integer field, that works
Then when i have a smart client open, i remove the vl from the integer field and attach it to a text field
Then yes i get an error in the smart client. But this is normal
Then i just close and open the solution and i dont get an error.
Then i change it back to the integer field, i get the error again and then close/open the solution and error gone and field works.
jcompagner:
if you can reproduce it then please let me know.
I just tried this. in the example above, integers valuelist attached to an integer field, that works
Then when i have a smart client open, i remove the vl from the integer field and attach it to a text field
Then yes i get an error in the smart client. But this is normal
Then i just close and open the solution and i dont get an error.
Then i change it back to the integer field, i get the error again and then close/open the solution and error gone and field works.
As mentioned, these steps didn’t work for me Johan - but I can see it’s unlikely to be fixable without being reproducible - and I cant at the moment! Sorry.