If I understand you correctly, Albert, I would create a one col table with just the three lines:
SORTONE TA TB TC Since the field they would be changing would be the listprice field, I could put your code in an on entry EEP in that field. That way I do not worry about them not skipping the field. Do you think that would work? Jim -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Albert Berry Sent: Wednesday, December 23, 2009 11:38 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: edit field First option - pain in the butt if there is any change later - is to create an eep on the exit from the field Model# based on the three model numbers you specified. A better way is to add a lookup value to the database that says that these models can be edited. This could be as simple as a one column table with Sortone in it that you can simply add or remove values that allow the price to be edited. You could add a T/F field to the model master table where Sortone is looked up. Working with the one column table, I would create an eep such as this. Sortone obviously has to be updated based on the model number before this will work properly -------------------------------------------------------- SET VAR fCount INTEGER SET VAR fSortone TEXT GETPROPERTY Sortone TEXTVALUE 'fModel#' SELECT COUNT(*) INTO fCount FROM EditableSortone + WHERE Sortone = .fSortone IF vCount = 1 THEN PROPERTY Comp_ListPrice READONLY 'FALSE' ELSE PROPERTY Comp_ListPrice READONLY 'TRUE' ENDIF RETURN -------------------------------------------------------- I would also add a row change eep that would be like this as suspenders to go with the belt. -------------------------------------------------------- PROPERTY Comp_ListPrice READONLY 'TRUE' RETURN -------------------------------------------------------- Jim Belisle wrote: > > In our Order entry form, under most circumstances I do not want the > entry people to be able to change the list price for items sold. > > There is however one case where it would be good for them to change > the list price. > > When we sell one product the list varies based on the additions to the > product. We do not want to have line items for those items because > the product is essentially the same with added gauges, etc. > > > > The field that determines the lookup for the list price is Model# > (componentID Order_Model). > > The field that would allow changing of the list price is called > Sortone. If this one is TA or TB or TC I would allow list price change. > > The field that would be changed is KPRSell (ComponentID Comp_ListPrice). > > > > I was thinking of using an On exit EEP in the Model# field > > > > Jim > > >
