No, there's no need to use the "custom" enumeration type, you just need to go in and switch the "Yes" name (and labels on all views) to "No", and the "No" name and labels to "Yes".
HOWEVER you must change the existing data to match the new mapping. I'd recommend using SQL to execute a command like the following (let's assume the form name is "SomeForm"): UPDATE SomeForm SET Text = CASE WHEN Text = 0 THEN 1 ELSE 0 END Note that I'm assuming that your enumeration doesn't have any other values besides Yes (currently mapped to 0) and No (currently mapped to 1). Hope this helps. -charlie On Fri, Apr 18, 2014 at 6:59 AM, vidyasagar kommu <[email protected] > wrote: > ** > Hi All, > > existing behaviour In a regualr form i have radio button field name > ‘Text’ = ‘YES’and Data base value as “0” and ‘Text'= ‘NO’ and the Data > base value as “1”. > There is no default value > > > > New requirement is 'Text'= ‘YES’ and database value should be “1” > and 'Text’= ‘NO’ then database value should be “0”. > ‘Text' field Default value should be “No” > > Could you please let me know how do I change the database Id of the > existing field i.e 'Text' > Is there any Impact on existing Orders ? > > Should we convert the field Linear to Custom ....If you go to field > properties under Attributies---we have option call Custom should we change > the data base ID ? > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
