pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive help / color / mirror / Atom feed From: Karsten Kaus <kk@kdschmid.de>
To: David Hartwig <daveh@insightdist.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] ODBC - MSysConf
Date: Fri, 12 Feb 1999 11:44:40 -0800
Message-ID: <36C484A8.1675@kdschmid.de> (raw )
References: <36C344C5.4A28@kdschmid.de >
<36C2EAA0.8DEE0FAB@insightdist.com >
David Hartwig wrote:
>
> Karsten Kaus wrote:
>
> > ok, in general it seems to be possible to connect Access97 ( not Access
> > 2.0! ?right? ) to postgres.
>
> I recall someone doing this successfully. The key here is that it needs to
> be running on Win95, Win98, or NT.
>
as far as I understood, the PostgreSQL driver is a 32-Bit program, so it
does
not show up when I'm using Access 2.0 to link tables, pity, but I can
live with that,
even it will cost money again.
> >
> > It works on ONE of my Computers in the office (486). On that computer
> > I cannot start the 32Bit-ODBC in the systemconfiguration, but I can
...
> > error 4307, that there is a Table called MSysConf on my server but
> > it does not have the expected format.
>
> You do not need this table on the server. The driver will report it as an
> error in the log file, but it should not be a problem to the application.
>
I read that before, but the case is slightly different. The table does
not exist.
I created the table at home, not here in the office. I just veryfied
dropping the table and got the message it woldn't exist.
Now access should notice that the table is missing, but it states the
table would
be there having a wrong format.
> Activate the CommLog in the driver settings and send a copy of the errant
> session. Its located in C:\psqlodbc*.log.
I did that in the driversetup. but it didn't log to C:\psqlodbc*.log
(I've seen and read them before, but now they are not created any more).
The log is in c:\sql.log. This file is also mentioned in the driver
setup.
So I think it's ok. The info contained looks a little different than in
the
psql*-files, but as fas as I see - the same info is contained:
--------------Here comes c:\sql.log ---------------------
MSACCESS fff27265:fff26281 ENTER SQLAllocConnect
HENV 0x00b30204
HDBC * 0x0062c910
MSACCESS fff27265:fff26281 EXIT SQLAllocConnect with return
code 0 (SQL_SUCCESS)
HENV 0x00b30204
HDBC * 0x0062c910 ( 0x00b31668)
MSACCESS fff27265:fff26281 ENTER SQLSetConnectOption
HDBC 0x00b31668
UWORD 103
UDWORD 20
MSACCESS fff27265:fff26281 EXIT SQLSetConnectOption with return
code 0 (SQL_SUCCESS)
HDBC 0x00b31668
UWORD 103
UDWORD 20
MSACCESS fff27265:fff26281 ENTER SQLDriverConnectW
HDBC 0x00b31668
HWND 0x000002b8
WCHAR * 0x00b30560 [ -3] ""
SWORD -3
WCHAR * 0x00b31734
SWORD 510
SWORD * 0x0062c966
UWORD 1 <SQL_DRIVER_COMPLETE>
MSACCESS fff27265:fff26281 EXIT SQLDriverConnectW with return
code 0 (SQL_SUCCESS)
HDBC 0x00b31668
HWND 0x000002b8
WCHAR * 0x00b30560 [ -3] ""
SWORD -3
WCHAR * 0x00b31734 [ 362]
"DSN=PostgreSQL;DATABASE=faxlog;SERVER=192.168.0.3;PORT=5432;UID=kk;PWD=<censored>;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS="
SWORD 510
SWORD * 0x0062c966 (362)
UWORD 1 <SQL_DRIVER_COMPLETE>
MSACCESS fff27265:fff26281 ENTER SQLGetInfo
HDBC 0x00b31668
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 51478
SWORD 2
SWORD * 0x0062c90e
MSACCESS fff27265:fff26281 ENTER SQLGetInfoW
HDBC 0x00b31668
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 51478
SWORD 2
SWORD * 0x0062c90e
MSACCESS fff27265:fff26281 EXIT SQLGetInfoW with return code 0
(SQL_SUCCESS)
HDBC 0x00b31668
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 51478
SWORD 2
SWORD * 0x0062c90e (2)
MSACCESS fff27265:fff26281 EXIT SQLGetInfo with return code 0
(SQL_SUCCESS)
HDBC 0x00b31668
UWORD 9 <SQL_ODBC_API_CONFORMANCE>
PTR 51478
SWORD 2
SWORD * 0x0062c90e (2)
MSACCESS fff27265:fff26281 ENTER SQLGetInfo
HDBC 0x00b31668
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x0062c8ac
SWORD 100
SWORD * 0x0062c916
MSACCESS fff27265:fff26281 ENTER SQLGetInfoW
HDBC 0x00b31668
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x00b31838
SWORD 200
SWORD * 0x0062c916
MSACCESS fff27265:fff26281 EXIT SQLGetInfoW with return code 0
(SQL_SUCCESS)
HDBC 0x00b31668
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x00b31838 [ 24] "PSQLODBC.DLL"
SWORD 200
SWORD * 0x0062c916 (24)
MSACCESS fff27265:fff26281 EXIT SQLGetInfo with return code 0
(SQL_SUCCESS)
HDBC 0x00b31668
UWORD 6 <SQL_DRIVER_NAME>
PTR 0x0062c8ac [ 12] "PSQLODBC.DLL"
SWORD 100
SWORD * 0x0062c916 (12)
MSACCESS fff27265:fff26281 ENTER SQLGetInfo
HDBC 0x00b31668
UWORD 46 <SQL_TXN_CAPABLE>
PTR 51328
SWORD 2
SWORD * 0x0062c742
MSACCESS fff27265:fff26281 ENTER SQLGetInfoW
HDBC 0x00b31668
UWORD 46 <SQL_TXN_CAPABLE>
PTR 51328
SWORD 2
SWORD * 0x0062c742
MSACCESS fff27265:fff26281 EXIT SQLGetInfoW with return code 0
(SQL_SUCCESS)
HDBC 0x00b31668
UWORD 46 <SQL_TXN_CAPABLE>
PTR 51328
SWORD 2
SWORD * 0x0062c742 (2)
MSACCESS fff27265:fff26281 EXIT SQLGetInfo with return code 0
(SQL_SUCCESS)
HDBC 0x00b31668
UWORD 46 <SQL_TXN_CAPABLE>
PTR 51328
SWORD 2
SWORD * 0x0062c742 (2)
MSACCESS fff27265:fff26281 ENTER SQLGetInfo
HDBC 0x00b31668
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 27128
SWORD 2
SWORD * 0x0062c742
MSACCESS fff27265:fff26281 ENTER SQLGetInfoW
HDBC 0x00b31668
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 27128
SWORD 2
SWORD * 0x0062c742
MSACCESS fff27265:fff26281 EXIT SQLGetInfoW with return code 0
(SQL_SUCCESS)
HDBC 0x00b31668
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 27128
SWORD 2
SWORD * 0x0062c742 (2)
MSACCESS fff27265:fff26281 EXIT SQLGetInfo with return code 0
(SQL_SUCCESS)
HDBC 0x00b31668
UWORD 23 <SQL_CURSOR_COMMIT_BEHAVIOR>
PTR 27128
SWORD 2
SWORD * 0x0062c742 (2)
MSACCESS fff27265:fff26281 ENTER SQLGetInfo
HDBC 0x00b31668
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 27130
SWORD 2
SWORD * 0x0062c742
MSACCESS fff27265:fff26281 ENTER SQLGetInfoW
HDBC 0x00b31668
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 27130
SWORD 2
SWORD * 0x0062c742
MSACCESS fff27265:fff26281 EXIT SQLGetInfoW with return code 0
(SQL_SUCCESS)
HDBC 0x00b31668
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 27130
SWORD 2
SWORD * 0x0062c742 (2)
MSACCESS fff27265:fff26281 EXIT SQLGetInfo with return code 0
(SQL_SUCCESS)
HDBC 0x00b31668
UWORD 24 <SQL_CURSOR_ROLLBACK_BEHAVIOR>
PTR 27130
SWORD 2
SWORD * 0x0062c742 (2)
MSACCESS fff27265:fff26281 ENTER SQLGetInfo
HDBC 0x00b31668
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 51332
SWORD 2
SWORD * 0x0062c87e
MSACCESS fff27265:fff26281 ENTER SQLGetInfoW
HDBC 0x00b31668
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 51332
SWORD 2
SWORD * 0x0062c87e
MSACCESS fff27265:fff26281 EXIT SQLGetInfoW with return code 0
(SQL_SUCCESS)
HDBC 0x00b31668
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 51332
SWORD 2
SWORD * 0x0062c87e (2)
MSACCESS fff27265:fff26281 EXIT SQLGetInfo with return code 0
(SQL_SUCCESS)
HDBC 0x00b31668
UWORD 1 <SQL_ACTIVE_STATEMENTS>
PTR 51332
SWORD 2
SWORD * 0x0062c87e (2)
MSACCESS fff27265:fff26281 ENTER SQLSetConnectOption
HDBC 0x00b31668
UWORD 101
UDWORD 0
MSACCESS fff27265:fff26281 EXIT SQLSetConnectOption with return
code 0 (SQL_SUCCESS)
HDBC 0x00b31668
UWORD 101
UDWORD 0
MSACCESS fff27265:fff26281 ENTER SQLAllocStmt
HDBC 0x00b31668
HSTMT * 0x0062c744
MSACCESS fff27265:fff26281 EXIT SQLAllocStmt with return code 0
(SQL_SUCCESS)
HDBC 0x00b31668
HSTMT * 0x0062c744 ( 0x00b31870)
MSACCESS fff27265:fff26281 ENTER SQLGetStmtOption
HSTMT 0x00b31870
UWORD 0
PTR 0x0062c6e8
MSACCESS fff27265:fff26281 EXIT SQLGetStmtOption with return
code 0 (SQL_SUCCESS)
HSTMT 0x00b31870
UWORD 0
PTR 0x0062c6e8
MSACCESS fff27265:fff26281 ENTER SQLSetStmtOption
HSTMT 0x00b31870
UWORD 0
UDWORD 60
MSACCESS fff27265:fff26281 EXIT SQLSetStmtOption with return
code 0 (SQL_SUCCESS)
HSTMT 0x00b31870
UWORD 0
UDWORD 60
MSACCESS fff27265:fff26281 ENTER SQLExecDirect
HSTMT 0x00b31870
UCHAR * 0x040ce9a0 [ -3] "SELECT Config, nValue FROM
MSysConf"
SDWORD -3
MSACCESS fff27265:fff26281 EXIT SQLExecDirect with return code
0 (SQL_SUCCESS)
HSTMT 0x00b31870
UCHAR * 0x040ce9a0 [ -3] "SELECT Config, nValue FROM
MSysConf"
SDWORD -3
MSACCESS fff27265:fff26281 ENTER SQLFetch
HSTMT 0x00b31870
MSACCESS fff27265:fff26281 EXIT SQLFetch with return code -1
(SQL_ERROR)
HSTMT 0x00b31870
MSACCESS fff27265:fff26281 ENTER SQLError
HENV 0x00b30204
HDBC 0x00b31668
HSTMT 0x00b31870
UCHAR * 0x0062c6ac (NYI)
SDWORD * 0x0062c6c8
UCHAR * 0x0089a9cc
SWORD 8192
SWORD * 0x0062c6de
MSACCESS fff27265:fff26281 ENTER SQLErrorW
HENV 0x00b30204
HDBC 0x00b31668
HSTMT 0x00b31870
WCHAR * 0x0062c25c (NYI)
SDWORD * 0x0062c6c8
WCHAR * 0x0062c268
SWORD 1024
SWORD * 0x0062c6de
MSACCESS fff27265:fff26281 EXIT SQLErrorW with return code 0
(SQL_SUCCESS)
HENV 0x00b30204
HDBC 0x00b31668
HSTMT 0x00b31870
WCHAR * 0x0062c25c (NYI)
SDWORD * 0x0062c6c8 (3)
WCHAR * 0x0062c268 [ 74] "Bindings were not allocated
properly."
SWORD 1024
SWORD * 0x0062c6de (74)
MSACCESS fff27265:fff26281 EXIT SQLError with return code 0
(SQL_SUCCESS)
HENV 0x00b30204
HDBC 0x00b31668
HSTMT 0x00b31870
UCHAR * 0x0062c6ac (NYI)
SDWORD * 0x0062c6c8 (3)
UCHAR * 0x0089a9cc [ 37] "Bindings were not allocated
properly."
SWORD 8192
SWORD * 0x0062c6de (37)
MSACCESS fff27265:fff26281 ENTER SQLError
HENV 0x00b30204
HDBC 0x00b31668
HSTMT 0x00b31870
UCHAR * 0x0062c6ac (NYI)
SDWORD * 0x0062c6c8
UCHAR * 0x0089a9fa
SWORD 8146
SWORD * 0x0062c6de
MSACCESS fff27265:fff26281 ENTER SQLErrorW
HENV 0x00b30204
HDBC 0x00b31668
HSTMT 0x00b31870
WCHAR * 0x0062c25c (NYI)
SDWORD * 0x0062c6c8
WCHAR * 0x0062c268
SWORD 1024
SWORD * 0x0062c6de
MSACCESS fff27265:fff26281 EXIT SQLErrorW with return code 100
(SQL_NO_DATA_FOUND)
HENV 0x00b30204
HDBC 0x00b31668
HSTMT 0x00b31870
WCHAR * 0x0062c25c (NYI)
SDWORD * 0x0062c6c8
WCHAR * 0x0062c268
SWORD 1024
SWORD * 0x0062c6de
MSACCESS fff27265:fff26281 EXIT SQLError with return code 100
(SQL_NO_DATA_FOUND)
HENV 0x00b30204
HDBC 0x00b31668
HSTMT 0x00b31870
UCHAR * 0x0062c6ac (NYI)
SDWORD * 0x0062c6c8
UCHAR * 0x0089a9fa
SWORD 8146
SWORD * 0x0062c6de
MSACCESS fff27265:fff26281 ENTER SQLFreeStmt
HSTMT 0x00b31870
UWORD 0 <SQL_CLOSE>
MSACCESS fff27265:fff26281 EXIT SQLFreeStmt with return code 0
(SQL_SUCCESS)
HSTMT 0x00b31870
UWORD 0 <SQL_CLOSE>
MSACCESS fff27265:fff26281 ENTER SQLFreeStmt
HSTMT 0x00b31870
UWORD 1 <SQL_DROP>
MSACCESS fff27265:fff26281 EXIT SQLFreeStmt with return code 0
(SQL_SUCCESS)
HSTMT 0x00b31870
UWORD 1 <SQL_DROP>
MSACCESS fff27265:fff26281 ENTER SQLDisconnect
HDBC 0x00b31668
MSACCESS fff27265:fff26281 EXIT SQLDisconnect with return code
0 (SQL_SUCCESS)
HDBC 0x00b31668
MSACCESS fff27265:fff26281 ENTER SQLFreeConnect
HDBC 0x00b31668
MSACCESS fff27265:fff26281 EXIT SQLFreeConnect with return code
0 (SQL_SUCCESS)
HDBC 0x00b31668
MSACCESS fff27265:fff26281 ENTER SQLFreeEnv
HENV 0x00b30204
MSACCESS fff27265:fff26281 EXIT SQLFreeEnv with return code 0
(SQL_SUCCESS)
HENV 0x00b30204
--------------------eof-----------------------------------
I verified again using pg_dumpall, that there is no table MSysConf.
And - even better: postmasters log says in that moment:
ERROR: msysconf: Table does not exist.
So I think I can be shure of that.
has anyone seen that before?
KK
view thread (5+ messages) latest in thread
Message-ID: <36C484A8.1675@kdschmid.de>
Permalink: ../36C484A8.1675@kdschmid.de/
Also on: postgresql.org/message-id/36C484A8.1675@kdschmid.de
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: kk@kdschmid.de, daveh@insightdist.com
Subject: Re: [INTERFACES] ODBC - MSysConf
In-Reply-To: <36C484A8.1675@kdschmid.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox