TMyQuery Options EnableBoolean bug

NoComprende · Post by **NoComprende** » Sun 29 Apr 2007 14:28

If you set EnableBoolean to false then, from what I can see,
if a tinyint field contains 1
FieldByName->AsInteger will return 1 but
FieldValues[] will return -1.

Antaeus · Post by **Antaeus** » Thu 03 May 2007 07:09

I could not reproduce the problem.
Please provide a piece of code or send me a complete small sample at evgeniyD*crlab*com to demonstrate it, including script to create and fill table.

Also supply me the following information:
- exact version of C++Builder;
- exact version of MyDAC. You can see it in the About sheet of TMyConnection Editor;
- exact version of MySQL server and MySQL client. You can see it in the Info sheet of TMyConnection Editor.

NoComprende · Post by **NoComprende** » Thu 03 May 2007 09:20

Apologies Antaeus, I've spent a couple of hours trying to reproduce this in a simple environment but am unable to do so. I'm afraid I had already amended all the original code to overcome the error. I'll resurrect the thread if I come accross it again.

Antaeus · Post by **Antaeus** » Thu 03 May 2007 14:02

Anyway please supply me the information I requested in my previous post.

Antaeus wrote:Also supply me the following information:
- exact version of C++Builder;
- exact version of MyDAC. You can see it in the About sheet of TMyConnection Editor;
- exact version of MySQL server and MySQL client. You can see it in the Info sheet of TMyConnection Editor.

NoComprende · Post by **NoComprende** » Thu 03 May 2007 14:24

BCB 6.0 (Build 10.166)

MyDAC 5.00.0.1

MySQL 5.0.27

If I remember correctly it involved newly created (but posted) records. These posted records showed the correct value when viewed in the MySQL query browser but, in BCB, inside an OnGetText method (implemented for a field that was dependant on the tinyint field value) the tinyint field returned -1 instead of 1 despite EnableBoolean being set to false. If the query was refreshed, everything then worked as it should.

Antaeus · Post by **Antaeus** » Thu 10 May 2007 12:36

Thank you for this information. We have reproduced this problem and fixed it. This fix will be included in the next MyDAC build. The next MyDAC build will be available in the nearest time.