Confused: TDBMemo fields locked while TDBEdit not

E

Ellen

Member
I have a problem with memo-fields (fields bound to TDBMemo/Varchar2) sometimes not being editable/locked, while edit-fields (bound to TDBEdit) are editable (in the same dataset, with a simple query not joining any tables). Inspecting the memos at runtime says ReadOnly=False, Enabled=True, so there's no indication the memos should be locked.

Anyone experienced something similar?

Ellen
 
There have been some issues with this in the past. What Direct Oracle Access version are you using?

------------------
Marco Kalter
Allround Automations
 
Version 3.4.3.

I've found the problem. It's related to me dynamically assigning FieldName, Datasource to some data aware components on a form. If I assign Datasource first, and then FieldName, that work ok for TDBEdit, but not for a TDBMemo (the TDBMemo becomes uneditable). If assigning Fieldname first, and then Datasource, then also the TDBMemo becomes editable (ie no problem).
(I was "unlucky" and assumed the "wrong" order made the most sense, so this took some time to figure out!)

Ellen
 
You must log in or register to reply here.
Back
Top