Skip site navigation (1) Skip section navigation (2)

Re: Access export overflow

From: Jeff Eckermann <jeff_eckermann(at)yahoo(dot)com>
To: Ken-ichi <kueda(at)nature(dot)berkeley(dot)edu>, pgsql-odbc(at)postgresql(dot)org
Subject: Re: Access export overflow
Date: 2004-09-17 18:53:55
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
I don't know what the problem is, but I would suspect
some weirdness in Access.

For exporting from Access to PostgreSQL, I suggest you
take a look at the "Database Migration Wizard" that
comes with PgAdminII (but not yet PgAdminIII,
regrettably).  I have had good experiences using that
wizard, which transparently does things like creating
appropriate sequences for your "autonumber" columns,
and creating referential integrity relationships based
on your Access setup.

--- Ken-ichi <kueda(at)nature(dot)berkeley(dot)edu> wrote:

> Hi folks.  I tried searching this list's archives
> for this problem but 
> came up short.  I have a fairly large table in MS
> Access 2000 (33 cols, 
> 3270 rows) that I'm trying to export to PostgreSQL
> 7.4.3.  When I clip 
> the table to only about 100 rows, the export runs
> fine, but when I try 
> to export the whole thing, I get an error window
> that says only 
> "Overflow."  This process generates the following
> error in my 
> postgresql.log file:
> ERROR:  relation "msysconf" does not exist
> The psqlodbc_xxxx.log written to my local machine
> ends with
> conn=124694520, query='ROLLBACK'
> conn=124694520, query='DROP TABLE "plot_data"'
> conn=124694520, PGAPI_Disconnect
> And the mylog_xxxx.log file doesn't seem to mention
> overflow anywhere, 
> but it does contain the lines
> [1900]**** PGAPI_ExecDirect: hstmt=131080744,
> statement='DROP TABLE 
> "plot_data"'
> [1900]PGAPI_ExecDirect: calling PGAPI_Execute...
> [1900]PGAPI_Execute: entering...
> [1900]PGAPI_Execute: clear errors...
> [1900]recycle statement: self= 131080744
> [1900]Exec_with_parameters_resolved: copying
> statement params: 
> trans_status=1, len=22, stmt='DROP TABLE
> "plot_data"'
> [1900]   stmt_with_params = 'DROP TABLE "plot_data"'
> [1900]      it's NOT a select statement:
> stmt=131080744
> [1900]send_query(): conn=131086712, query='DROP
> TABLE "plot_data"'
> [1900]send_query: done sending query
> Can anyone tell me what's going on, and how to fix
> it?
> Thanks.
> -Ken-ichi
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?

Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish. 

In response to

pgsql-odbc by date

Next:From: Scot LoachDate: 2004-09-19 14:29:07
Subject: segfault when disconnecting from db with server side prepare
Previous:From: mikDate: 2004-09-17 09:32:39
Subject: SQLDescribeCol before SQLExcecute call problerm

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group