Parameter | Description |
---|---|
iField | Table column to check |
By default it returns False, which means that while the field will be NoPut, you can enter values for finding purposes. This is the most flexible option. Some developers prefer that the DEO treat this is non-enterable (DisplayOnly).
Function Field_CommitNoEnterOnIndex Integer iField Returns Boolean
Call: | Get Field_CommitNoEnterOnIndex iField to BooleanVariable |
Called when the DataDictionary (DD) needs to determine if a committed table column that has an index should support entry.
By default it returns False, which means that, while the field will be NoPut, you can enter values for finding purposes. This is the most flexible option. Some developers prefer that the data entry object (DEO) treat this is as non-enterable (DisplayOnly). If so, you can augment this function to return True.
This was made a function instead of a property so you can easily control this at the sub-class level (same preference for your entire application) and so you can alter this on a column by column basis.
For example, adding this to a DD subclass, DD Class or DD object, would make all indexed, committed column DisplayOnly.
Function Field_CommitNoEnterOnIndex Integer iField Returns Boolean Function_Return True End_Function
Adding the following to your order entry sample workspace's Order.vw view, would make a single column (Order.Order_Date) DisplayOnly, while all other committed index columns would be NoPut, but allow entry. This assumes Order.Order_Date is indexed, has DD_COMMIT set and that the OrderHea record is actually committed.
Function Field_CommitNoEnterOnIndex Integer iField Returns Boolean // if date field, return True (noEnter) or else return false (can enter for finding but will be noput) Function_Return (RefTable(OrderHea.Order_Date)=iField) End_Function