I have an attribute with a list of choices. I want the deafult to be blank and if a choice is selected by mistake that the user can blank the entry.
To get around the issue, I have added an entry in th choice of say 4 spaces and added this as the default.
This works fine on my Derby and SQL databases for testing, but when I place on the client system the 'blank' choice (or spaces choice) is not available in the list.
As it is just a character value in the choices, why would this not transfer over in the new BSV ?
Blank entry in look up
-
- Posts: 7525
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
-
- Posts: 7525
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
Hi,
I agree that there should be no difference but I can confirm there is. I removed the 'blank' choice and entered a new choice of N/R to get around the issue and while it is clearly in my system it is not in the client one. Other changes applied at the same time however are in the client system.
Very strange. Is there access to a database table that stores this information ?
DV
I agree that there should be no difference but I can confirm there is. I removed the 'blank' choice and entered a new choice of N/R to get around the issue and while it is clearly in my system it is not in the client one. Other changes applied at the same time however are in the client system.
Very strange. Is there access to a database table that stores this information ?
DV
-
- Posts: 7525
- Joined: Sun Apr 24, 2005 12:36 am
- Contact: