[Properties (by Name)] [Methods (by Name)]
Like tdblookupbuffer, but each bound DB field is a memo whose text is split into one array row per line, converting each line to the array's type (and from UTF-8 for text fields)
Source position: mselookupbuffer.pas line 423
type tdbmemolookupbuffer = class(tcustomdblookupbuffer) |
public |
constructor create(); override; |
published |
property datasource: tdatasource; |
property textfields: tdbfieldnamearrayprop; |
property integerfields: tdbfieldnamearrayprop; |
property floatfields: tdbfieldnamearrayprop; |
end; |
|
Like tdblookupbuffer, but each bound DB field is a memo whose text is split into one array row per line, converting each line to the array's type (and from UTF-8 for text fields) |
|
| | | ||
| | | ||
| | | ||
|
Holds several parallel, integer-indexed arrays |
|
| | | ||
| | | ||
|
Extends the FPC tcomponent with object linking facilities and the like; base of every MSEgui component |
|
| | | ||
tcomponent,ievent,iificommand,iificlient |
||
| | | ||
| | | ||
TObject |
Like tdblookupbuffer, but each bound DB field is a memo whose text is split into one array row per line, converting each line to the array's type (and from UTF-8 for text fields); integerfields/ floatfields/textfields can therefore name any DB field convertible to the corresponding type, not just fields of that exact type. The buffer's row count is the smallest number of lines produced by any of the bound fields — longer fields are truncated.