char field corrupted

[Ludek]

following scenario:
delphi 2009, newest sdac.
fastmm4 with fulldebugmode activated.
one empty table with one char(60) field.
one simple form with tdbedit, tmsquery, tdatasource, tmsconnection and tdbnavigator

user writes an "a" to the edit field and presses "post" in the navigator.
sdac stores following to the char(60) field (converted to hex):

0x610032F67536808080808080202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020

those characters after "00" are making BIG trouble in non-sdac applications like ado.net.
please, could you make the char field clear?

note: without fulldebug, i get following in the char field

0x610020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020

it seems, you are storing data from memory areas, that don't belong to you.

thanks for your help, Ludek.

[Ludek]

next info:
using d2006 and sdac 4.35.1.16 everything is ok, with or without fastmm4 fulldebugmode i always get following:

0x612020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020202020

which is perfect - even the rather unhappy 00 character isn't there.

[Dimon]

I could not reproduce the problem.
Please send me a complete small sample to dmitryg*devart*com to demonstrate it, including a script to create and fill table.

[Ludek]

did you really try using following

select cast(col as binary(60)) from testtable

? i'll test you the project soon...

[Ludek]

example sent. it's really nothing more than i've already written.

[Dimon]

Thank you for information. We have reproduced this problem and fixed it. This fix will be included in the next SDAC build.

[Ludek]

When will the next sdac build be available?

[Dimon]

The next SDAC build will be released in the course of the next week.

[Ludek]

Are you sure? there are only a few hours remaining from this week...

[Ludek]

Wow, now! thanks