Change TUniTable table name property at runtime

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
testpresta
Posts: 32
Joined: Sat 07 Jun 2014 19:41

Change TUniTable table name property at runtime

Post by testpresta » Sun 26 Oct 2014 21:25

Hello

I have two tables which have the same fields structure.
The same screen and the same TUniTable component is used for the two tables.
When the screen is opened, i change TUniTable property.

It works very well for the first table.

But when i change to the second, my fields are not available.

This does not work:

Code: Select all

MyTableField1.Value:='test';
This work:

Code: Select all

MyTable.FieldByName('Field1').asstring:='test';
I want to make work the first code.
Is it a TUnitable bug ?

Thanks

testpresta
Posts: 32
Joined: Sat 07 Jun 2014 19:41

Re: Change TUniTable table name property at runtime

Post by testpresta » Sun 26 Oct 2014 21:32

In fact the 2 codes does not work.
I just close UniTable component, then change table name propery and the open (with filter)
Should i refresh something ?

AlexP
Devart Team
Posts: 5530
Joined: Tue 10 Aug 2010 11:35

Re: Change TUniTable table name property at runtime

Post by AlexP » Mon 27 Oct 2014 05:39

Hello,

We cannot reproduce the problem. Please clarify the versions of the IDE and UniDAC. In addition, specify the name of the DB you are working with, and send the table creating script and the small sample reproducing the problem to alexp*devart*com .

testpresta
Posts: 32
Joined: Sat 07 Jun 2014 19:41

Re: Change TUniTable table name property at runtime

Post by testpresta » Thu 30 Oct 2014 09:44

I cannot reproduce the problem on a simple project
I think the problem is caused by Filter.
I rewrite my code without Filter and it is fine

Thanks

AlexP
Devart Team
Posts: 5530
Joined: Tue 10 Aug 2010 11:35

Re: Change TUniTable table name property at runtime

Post by AlexP » Fri 31 Oct 2014 08:19

If you manage to create a simple application reproducing the problem, please send it to us - and we will investigate this behavior once more.

Post Reply