| Make field non editable [message #468347] |
Thu, 29 July 2010 16:23  |
coolguy01
Messages: 64
Registered: August 2006
|
Member |
|
|
HI,
I have a field on the form which is a database field and the value is populated by a LOV. The user should not be able to edit the value selected or enter his own values in the field. Basically the field should only be populated by the lov and should not be editable.
I tried using the SET_ITEM_PROPERTY('XX.XX', UPDATE_ALLOWED, PROPERTY_FALSE); but this only disable update against existing value. If a user selects a new value from LOV that can be edited. Let me know how to solve this
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Make field non editable [message #468519 is a reply to message #468516] |
Fri, 30 July 2010 08:54  |
cookiemonster
Messages: 13963
Registered: September 2008
Location: Rainy Manchester
|
Senior Member |
|
|
So does validate from list.
I'm not saying your wrong necesarily, guess it depends on your definition of long, I'm not a big fan of list items where the item count goes into double digits.
|
|
|
|
|
|
| Re: Make field non editable [message #468525 is a reply to message #468523] |
Fri, 30 July 2010 09:30 |
cookiemonster
Messages: 13963
Registered: September 2008
Location: Rainy Manchester
|
Senior Member |
|
|
Some thing else to bare in mind - if the list isn't static LOV's are a lot better than list items.
Reason being that if you try to query a record where the current value of the column used for the list item doesn't match any of the values the list item currently allows, then oracle forms silently rejects the record. It doesn't appear and forms doesn't tell you it's skipped it. That's caused more than a few panics over the years - "Where's my data gone!!!".
You can get around that by setting the "Mapping of Other Values" property but I very rarely used that since you can't normally say it's ok to treat some value as some other value.
You can get the same issue with radio groups as well.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
