When using TOraTable in master-detail mode (at least as detail dataset, have not tested as master dataset) and Options.ExtendedFieldsInfo='true' - all fields become read-only at runtime (in spite of the fact that in design-time all of them have property ReadOnly=false, TOraTable object also have ReadOnly=false) and as consequence, the dataset does not allow to edit and insert record (more precisely, to 'Post' changes) because error "'Field '...' cannot be modified'" occured.
If master-detail relationship is turned off or Options.ExtendedFieldsInfo set to 'false' - then all ok, dataset become editable.
note: by default object of type TOraTable have property Options.ExtendedFieldsInfo='true'.
ODAC 6.00.0.5: Problem with TOraTable + Options.ExtendedFieldsInfo=true
ODAC 6.00.0.5: Problem with TOraTable + Options.ExtendedFieldsInfo=true
Last edited by tuasal on Tue 17 Apr 2007 05:35, edited 1 time in total.
-
Challenger
- Devart Team
- Posts: 925
- Joined: Thu 17 Nov 2005 10:53
When the ExtendedFieldsInfo option is True, TOraDataSet requests an additional information about updating object and its fields. If SetFieldsReadOnly option is True, TOraDataSet sets the ReadOnly property for all fields according to this information.
We couldn't reproduce this problem. Please send to odac*crlab*com a complete sample that demonstrates this problem and include script to create server objects.
We couldn't reproduce this problem. Please send to odac*crlab*com a complete sample that demonstrates this problem and include script to create server objects.
> When the ExtendedFieldsInfo option is True,
> TOraDataSet requests an additional information
> about updating object and its fields. If SetFieldsReadOnly > option is True, TOraDataSet sets the ReadOnly property > for all fields according to this information.
Yes, I read the Help.
But i am speaking not about 'readonly'-fields. And Dataset earlier was accessible for editing (before ODAC 6.x)!
Today i have found another, simple and more a bright example.
There is a form for editing the simple table using TOraTable. Migration from the ODAC 5.x to 6.x made, thus of any changes in the form of was not made. Earlier the form allowed to edit the table. After migration to the ODAC 6.x - editing became inaccessible, since DataSet.CanModify=false.
We look at property DataSet.Options.ExtendedFieldsInfo - it's value is 'true'! Put 'false'... After that all safely works as earlier.
Something not that with property ExtendedFieldsInfo...
It is expected, that ExtendedFieldsInfo should be equal 'true'. But why it forces Dataset to become read-only (all Dataset, instead of separate fields), and for TOraTable exactly (TOraQuery - like all is ok). Here in what a question.
ps. i am using Oracle 9.2.0.7
> TOraDataSet requests an additional information
> about updating object and its fields. If SetFieldsReadOnly > option is True, TOraDataSet sets the ReadOnly property > for all fields according to this information.
Yes, I read the Help.
But i am speaking not about 'readonly'-fields. And Dataset earlier was accessible for editing (before ODAC 6.x)!
Today i have found another, simple and more a bright example.
There is a form for editing the simple table using TOraTable. Migration from the ODAC 5.x to 6.x made, thus of any changes in the form of was not made. Earlier the form allowed to edit the table. After migration to the ODAC 6.x - editing became inaccessible, since DataSet.CanModify=false.
We look at property DataSet.Options.ExtendedFieldsInfo - it's value is 'true'! Put 'false'... After that all safely works as earlier.
Something not that with property ExtendedFieldsInfo...
It is expected, that ExtendedFieldsInfo should be equal 'true'. But why it forces Dataset to become read-only (all Dataset, instead of separate fields), and for TOraTable exactly (TOraQuery - like all is ok). Here in what a question.
ps. i am using Oracle 9.2.0.7
-
Challenger
- Devart Team
- Posts: 925
- Joined: Thu 17 Nov 2005 10:53