New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access-related multi DB problem [ODBC32] #32
Comments
Commented by: Jorge Andres Brugger (jbrugger) Query log using build 142 |
Modified by: Jorge Andres Brugger (jbrugger)Attachment: SQL.LOG.B142.7z [ 10600 ] |
Commented by: Jorge Andres Brugger (jbrugger) Query log using build 144 |
Modified by: Jorge Andres Brugger (jbrugger)Attachment: SQL.LOG.B144.7z [ 10601 ] |
Commented by: Jorge Andres Brugger (jbrugger) Much small sample log. Build 142 output. |
Modified by: Jorge Andres Brugger (jbrugger)Attachment: SQL.142.LOG.7z [ 11001 ] |
Commented by: Jorge Andres Brugger (jbrugger) Log output for build 145. Smaller than previous 144 attach. |
Modified by: Jorge Andres Brugger (jbrugger)Attachment: SQL.145.LOG.7z [ 11002 ] |
Commented by: @alexpotapchenko Please test this build (145 too). It includes a possible correction of this problem only . |
Modified by: @alexpotapchenkoAttachment: OdbcFb32.zip [ 11010 ] |
Commented by: Jorge Andres Brugger (jbrugger) Alexander, my test case now works fine. I´ll keep this build (145) installed on my dev machine and inform what I discover, but this bug seems to be solved and patch should be commited. Thanks! |
Modified by: @alexpotapchenkoassignee: Vladimir Tsvigun [ praktik ] => Alexander Potapchenko [ lightfore ] |
Modified by: @alexpotapchenkostatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.0 Beta [ 10043 ] |
Modified by: @alexpotapchenkostatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Jorge Andres Brugger (jbrugger)
Attachments:
SQL.142.LOG.7z
SQL.145.LOG.7z
OdbcFb32.zip
SQL.LOG.B142.7z
SQL.LOG.B144.7z
Attached are two files, both of them are logs of exactly same Access query, one using ODBC build 144 and the other using ODBC build 142.
b142 works fine, b144 has problems with checks.
Query is:
IINSERT INTO CLIENTES ( CODIGO, NOMBRE, PERSONA_CONTACTO, TELEFONO, FAX, CORREO_ELECTRONICO, DOMICILIO, CODIGO_POSTAL, LOCALIDAD, PROVINCIA, CUIT, NUMERO_INGRESOS_BRUTOS, CODIGO_SITUACION_IVA, TIPO_DOCUMENTO_EMISION, HABILITADO_CUENTA_CORRIENTE, TOPE_CREDITO, SUSPENDIDO, MOSTRAR_OBSERVACIONES, OBSERVACIONES, NUMERO_LEGAJO, ENTIDAD_LEGAJO, CREDITOS_SOLO_TITULAR, DESCUENTO_POR_PLANILLA, CUENTA_CORRIENTE_UNIFICADA, UPDATE_TIMESTAMP )
SELECT CLIENTES2.CODIGO, CLIENTES2.NOMBRE, CLIENTES2.PERSONA_CONTACTO, CLIENTES2.TELEFONO, CLIENTES2.FAX, CLIENTES2.CORREO_ELECTRONICO, CLIENTES2.DOMICILIO, CLIENTES2.CODIGO_POSTAL, CLIENTES2.LOCALIDAD, CLIENTES2.PROVINCIA, CLIENTES2.CUIT, CLIENTES2.NUMERO_INGRESOS_BRUTOS, CLIENTES2.CODIGO_SITUACION_IVA, CLIENTES2.TIPO_DOCUMENTO_EMISION, CLIENTES2.HABILITADO_CUENTA_CORRIENTE, CLIENTES2.TOPE_CREDITO, CLIENTES2.SUSPENDIDO, CLIENTES2.MOSTRAR_OBSERVACIONES, CLIENTES2.OBSERVACIONES, CLIENTES2.NUMERO_LEGAJO, CLIENTES2.ENTIDAD_LEGAJO, CLIENTES2.CREDITOS_SOLO_TITULAR, CLIENTES2.DESCUENTO_POR_PLANILLA, CLIENTES2.CUENTA_CORRIENTE_UNIFICADA, CLIENTES2.UPDATE_TIMESTAMP
FROM CLIENTES2 LEFT JOIN CLIENTES ON CLIENTES2.CODIGO = CLIENTES.CODIGO
WHERE (((CLIENTES.CODIGO) Is Null));
Commits: ec0dca9 fe04638 5410be9
The text was updated successfully, but these errors were encountered: