Bug #7771 Optimize Column Width

• Submitted: 10 Jan 2005 14:47
• Modified: 26 Jan 2005 19:28
• Reporter: [ name withheld ]
• Status: Duplicate
• Category: Connector / ODBC
• Severity: S3 (Non-critical)
• Version: 3.51.10
• OS: Microsoft Windows (Window)
• CPU Architecture: Any

[10 Jan 2005 14:47] [ name withheld ]

Description:
The C++ builder application is working fine with 3.51.06. But after update to 3.51.10, even select the options:'Don't optimize column width' and 'Return matching rows', the editing column will stay with the previous column size not the default size difined in the database. 

How to repeat:
For example, if the field defined as following: test_fd varchar(50). When you initial setup test_fd as 'Test' through C++ builder application then change this field to 'something else' in the application. The MyODBC will still think the size as 4 then save the 'some' to the database. But in the release 3.51.06, it will save the 'something else' into the databse. Why does not the option 'don't optimize column width' work on 3.51.10?

[26 Jan 2005 20:16] [ name withheld ]

This bug isn't the same problem of bug #7860. It is happened when edit the string field it shorten the length of new enter string equal to the last entered string's length. It didn't use the defined length in the database. Please review the problem again.

[31 Jan 2005 22:55] [ name withheld ]

Somehow I copy all the myodbc dll and lib files from old version (3.51.10?) not the current release. Everything is working fine. Here is list of the dll/lib file and their created time:
File                         3.51.10-?                3.51.10-2
myodbc3.dll              10/25/2004              12/18/2004      
myodbc3.lib              10/25/2004               3/4/2003
myodbc3d.dll             3/4/2003                  3/4/2003
myodbc3S.dll             10/25/2004
myodbc3S.lib             10/25/2004               12/18/2004

There is also a problem on removing current package. It didn't remove all the above dll and lib files.