Page 1 of 1

Issues with TVirtualTable

Posted: Thu 24 Jul 2014 14:15
by m.ghilardi
I use TVirtualTable a lot. I've found a couple of issues:

1) It does not support ftOraTimeStamp field type. (!!!)
2) FindField(UnicodeString) is not properly implemented (always returns NULL if the VT is closed), FieldDefs.Find() is an option but it raises an exception if the field is not there... so usually I scan FieldDefs with a for loop

Question:
How do I clear all field definitions? DeleteFields? Fields->Clear()? FieldDefs->Clear()?

Feature Requests:
1) CopyField(TField* , UnicodeString fieldname) copies a tfield with the option to change its name
2) DeleteFieldIfPresent

Re: Issues with TVirtualTable

Posted: Mon 28 Jul 2014 08:03
by AlexP
Hello,

1) We have added support for ftOraTimeStamp in VT, this fix will be included to the next VT table.
2) The FindField method is implemented in the standard DB module in the TDataSet class and it is not virtual, therefore we can't modify it's behavior.
In order for this field to return a field by name, the DataSet must be open, or Persistent fields must be created.
This is applied to the TFieldDefs.Find method as well: the method is not virtual, and it raises an exception if a field is not found.
3) To clean FieldDefs, you should use the Clear method.

You can suggest new features at our UserVoice page: https://devart.uservoice.com/forums/104 ... omponents/ .

Re: Issues with TVirtualTable

Posted: Mon 28 Jul 2014 13:38
by m.ghilardi
I'm glad to hear that VT is evolving, this is a very important component for us.
Thanks.

Re: Issues with TVirtualTable

Posted: Tue 29 Jul 2014 06:20
by AlexP
You are welcome. If you have any more questions or suggestions regarding our components, please contact us again.