When we write to a memo field, if the data is between 33 and 64 bytes long it appears to be corrupted. Access 2003 displays it as #Error, other ODBC tools can't read it. Access 2007 appears to handle it OK, but we're not quite sure about that.
When we call SQLGetData (in another tool) the Access ODBC driver reports:
Error code 0xfffffb4a; sqlstate HY000; : error 0xffffffff; [Microsoft][ODBC Microsoft Access Driver] Cannot open database '|'. It may not be a database that your application recognizes, or the file may be corrupt.
We're using version HXTT Access v3.1.011.
We can work around this problem in the immediate term by padding the data so that its size doesn't fall in the range 33-64 bytes, but obviously that's not a good permanent solution. Also, we're concerned that there may be other sizes that will give the same problem.
So my questions are:
1. Can you fix it?
2. Can you explain it? We need to be confident that there is no other data size that will cause the same problem.
>2. Can you explain it?
Thank for your report. It should be a few bugs in MS Access development. MS Access 2000 supported it, but 2003 failed, then 2007 resupported it:(
>We need to be confident that there is no other data size that will cause the same problem.
Until now, we just found those above incompatible information.
>1. Can you fix it?
Don't worry. Please download the latest package AFTER about 24 hours. Then run once "update yourtable set yourIssueColumn=RTRIM(yourIssueColumn);" with HXTT Access. That's all.
Thanks for the very quick response. Version 3.1.013 does indeed seem to fix the problem.
I wonder could you explain briefly what the problem was? What was special about the range 33-64 bytes? How can we be confident that there aren't other similar problem ranges we should watch out for?
>>MS Access 2000 supported it, but 2003 failed, then 2007 resupported it:(
>I wonder could you explain briefly what the problem was?
Don't worry. It seems that MS does some minor incompatible changes on their different versions. We need just to find an easy solution to skip those issues.
>How can we be confident that there aren't other similar problem ranges
> we should watch out for?
You needn't to care for too much since MS won't make too much incompatible bugs. If you found, just let us know. HXTT will solve it ASAP.