About 6 months ago, we upgraded from v6.5x to v7.0x - not sure of the exact version, but do know that we still have the 8k text limit that has been recently solved with a limit of 32k.
For both databases, we have had a MS Access front-end, that accessed Postgres via an ODBC driver. The driver was just upgraded to v7.x (obtained from odbc.postgresql.org).
My problem is with intrepretation of a time field. Previously, 10:00 meant 10:00, but now anytime 10:00 is entered, the database shows 9:59, but if I enter 10:00.05, I can get 10:00.00. Worse, because the 'change' is made, Access thinks that there is another user, and then locks the record, preventing the only user from making any changes.
Is this a Postgres bug, an issue with the ODBC driver, or something else?
Unless someone can tell me what may problem may be, I'm probably looking at 'fixing' Access with a work-around, something I don't want to do.
For both databases, we have had a MS Access front-end, that accessed Postgres via an ODBC driver. The driver was just upgraded to v7.x (obtained from odbc.postgresql.org).
My problem is with intrepretation of a time field. Previously, 10:00 meant 10:00, but now anytime 10:00 is entered, the database shows 9:59, but if I enter 10:00.05, I can get 10:00.00. Worse, because the 'change' is made, Access thinks that there is another user, and then locks the record, preventing the only user from making any changes.
Is this a Postgres bug, an issue with the ODBC driver, or something else?
Unless someone can tell me what may problem may be, I'm probably looking at 'fixing' Access with a work-around, something I don't want to do.