Property Boolean pbBypassDDFieldBuffer
| Read Access: | Get pbBypassDDFieldBuffer to BooleanVariable |
| Write Access: | Set pbBypassDDFieldBuffer to BooleanVariable/Value |
Determines whether a data entry object (DEO) that uses extended columns should bypass updating the DataDictionary (DD) and perform updates directly against the global table buffer.
If you wish to use DD Field_Option, such as DD_Required, Field_Entry_msg or exit messages, with text columns, you should set this property to False.
Prior to revision 17.0, with Windows DEOs, the DDs and DEOs only partially supported a DD representation of text columns. Text column data was moved directly between the table buffer and the DEO bypassing the DD buffer. Most of the time this did not matter (which is why we did this). There are times when this proves to be a limitation.
With WebApp and with batch processes, you could use DD text columns but you had to explicitly specify in your DDO that you wanted to use extended DD columns.
Now, text DEOs (cDbTextEdit and cDbRichEdit) are full DEOs and can use the local DD buffers for text columns, just like the other DD columns. For backwards compatibility purposes, this is optional.
In addition, you no longer need to specify that you want to define an extended column - it's automatic. Previously, you needed to declare that you wanted an extended DD Text column with the message DefinedExtendedField or DefineAllExtendedFields. This is no longer required. The first time you send a message that needs an extended column; it will be created for you. This means you no longer need to use these messages in WebApp WBOs and batch process BOs.
pbBypassDDFieldBuffer, introduced in DataFlex revision 17.0, has been added to all DEOs, which will allow you to determine if a DEO that uses extended columns should bypass updating the DD and perform updates directly against the file buffer. When set to True, the bypass is in effect and the text column DEOs in windows will behave as they always did.
The default is True for the cDbTextEdit and cDbRichEdit classes, for compatibility reasons.
The legacy class Edit does not use this feature at all and works as it always did.