Bug #24535 | Notorious #DELETED problem when linking tables in Access and BIGINT PK | ||
---|---|---|---|
Submitted: | 23 Nov 2006 10:12 | Modified: | 28 Mar 2008 18:18 |
Reporter: | Tonci Grgin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | 5.1 | OS: | Windows (Win XP Pro (SP2)) |
Assigned to: | Jess Balint | CPU Architecture: | Any |
Tags: | ODBC, ODBC5-RC |
[23 Nov 2006 10:12]
Tonci Grgin
[17 Oct 2007 14:49]
Susanne Ebrecht
Hi Tonci, thanks for writing a bug report. Susanne
[19 Oct 2007 12:57]
Susanne Ebrecht
The bug #26343 is a duplicate of this bug here.
[22 Oct 2007 16:49]
Susanne Ebrecht
Bug #28640 is a duplicate of this bug here.
[29 Oct 2007 8:08]
Susanne Ebrecht
This is a duplicate of bug #31308
[29 Oct 2007 11:37]
Susanne Ebrecht
Verified as described for MyODBC v5.1 by using MS Access 2007.
[4 Dec 2007 0:30]
Jess Balint
Added FLAG_DFLT_BIGINT_BIND_STR to map SQL_BIGINT to SQL_C_CHAR when calling SQLBindParameter() with SQL_C_DEFAULT. This is beha
Attachment: bug24535.diff (application/octet-stream, text), 2.00 KiB.
[6 Dec 2007 16:55]
Lawrenty Novitsky
code looks ok, but i don't have access to check if it really works, but i trust you that it does :) first that comes to mind that it requires checkbox in gui to be added. although automatic detection of ms access should be enough, at least for beta.
[17 Mar 2008 19:07]
Jess Balint
Committed as rev 1074 and will be released in 5.1.3.
[28 Mar 2008 18:18]
MC Brown
A note has been added to the 5.1.3 changelog: Using a linked table in Access 2003 where the table has a BIGINT column as the first column in the table, and is configured as the primary key, shows #DELETED for all rows of the table.