Cannot convert <type1> to <type2>

[felixbcastillo]

I could not find the issue/cause!

I returned back to version 7.2.7 and everything is fine!

[MaximG]

Thank you for the information. We will definitely find a solution to the problem. To the analyze the provided description given please specify:

- is the described issue reproduced after installing the night build unidac73d25pro_05_09_2018 ?
- does the issue occur only at design-time ?
- do similar steps using UniDAC 7.2.7 cause the error ?

Please describe in detail the steps you perform in the IDE which lead to an incorrect result.

[felixbcastillo]

- is the described issue reproduced after installing the night build unidac73d25pro_05_09_2018 ?
YES, IT IS REPRODUCED AFTER NEW BUILD

- does the issue occur only at design-time ?
AT BOTH, DESIGN TIME AND RUN TIME
*Now it on SUM fields if a record is created in the virtual table, if you delete, clear or begin with empty values...all SUM values result on NULL/Empty

- do similar steps using UniDAC 7.2.7 cause the error ?
NO, v7.2.7 WORKS FINE!

[MaximG]

Unfortunately, we still cannot reproduce the described error using unidac73d25pro_05_09_2018. Therefore,
for further issue investigation, please compose and send us a small full FMX-application which when running clearly demonstrates the issue. Fill the VirtualTable component used in this application with the data,
which reproduce the described error after using the SUM function. Please send the sample
via the e-support form (https://www.devart.com/company/contactform.html)

[felixbcastillo]

Please download and run this sample:
https://mega.nz/#!4Q8UAYTR!nRULX44kjLj9 ... V8KIdGM8vk

Press the first button to add record sometimes to see it works begining with a record pre-inserted
It is Ok!

Now press the second button to clear the VirtualTable or begin with VirtualTable cleared
Then press the first button to add records, if you can confirm...SUM values result in NULL/Empty Values

Can you confirm it please?

Thank you in advanced!

[MaximG]

Thank you for sending the sample. We carefully investigated it and reproduced the error related to the work of the Refresh method. We know about its existence and work on its elimination. We will try to include the required fixes in one of the next versions of our product. As a workaround at present, use the methods calls :

VirtualQuery.Close;
VirtualQuery.Open;

instead of VirtualQuery.Refresh