I can follow the logic of why this might be happening. The Alias is view-specific but the Value is not. Since you are in Best Practice mode creating a new field will automatically created it as an overlaid field. This allows you to change the Value. Since the field isn't in a view it isn't in a view overlay so the Dev Studio dialog won't let you change the Alias because it is verifying that a display property is tied to a view overlay.
It may be a defect but I understand how it likely ended up that way (although does an Alias not in a view provide any value?). I bet if you add the filed to the view, then add it to the view overlay you can change the Alias. From there you can remove the field from the view again. On that note... Now that Dev Studio is aware of and allows fields not in any view (you no longer have to get tricky to achieve this) you can remove a field from the last view and it will not be deleted as in previous versions. I verified this recently with 8.1. Not sure if this has been the case since overlays were introduced in 7.6.04 so proceed with caution. Jason On Mar 18, 2014 3:07 PM, "Terje Moglestue" <[email protected]> wrote: > ** > > Is this a fault? It should be easy to reproduce. > > I got a OOB form where overlay is already created. I then want to create a > new Selection field that is not in any view. Here is how I do it: > > - Open form where the overlay is created. > > - Right click on the default view. Select "Create a New Field", > "In No View" and "Selection Field". > > - The new field is created. I fine the new field using the > Outline. Click on Attributes, Selections to update the valid Selections. > > - The Selection dialog pops up with one record Default 1. > > - I now want to change the Selection Value and the Alias. I click > on the 'Default 1' in the Selection Values column. This allow me to update > the value. > > - Click on the Alias is impossible. I can click - but nothing > happened. I am unable to change the Alias value. > > - I can add a new selection. Same time. > > Using the menu Form, Create a New Field, In No View. Same thing. > > Let's try to create a new field within the current view. Well the option > is there - but the different field types are all disabled. Is the overlay > corrupt? > > I am working in Best Practice Customization Mode. > > Regards, > Terje > > > _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"
