pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Hartwig <daveh@insightdist.com>
To: Matthew Hagerty <matthew@wolfepub.com>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] postgresODBC and Symantec dbAnywhere/Visual Cafe, broken?
Date: Wed, 05 Aug 1998 14:25:02 -0400
Message-ID: <35C8A37E.B1F41333@insightdist.com> (raw)
References: <3.0.1.32.19980805131620.006a496c@wolfepub.com>

1.   What version of the driver?

2.  Could you activate the CommLog in the drive setup and send the result of a
minimal test.  The log file will be found in C:\psqlodbc.log .

Matthew Hagerty wrote:

> Greetings,
>
> I'm going to get all these interfaces working if it kills me! ;)
>
> I have dbAnywhere running, I have an ODBC driver for my database
> (PostgreSQL) installed and working, and dbAnywhere makes a connection okay.
>  The only problem I have is when I try to select a table using a wizard (or
> in the recordDefinition->Table Name property, or in the dbNavigator), I get
> the following error:
>
> dbAnywhere window:
>
>     Message: [Symantec][dbANYWHERE Server][Version: 1.1a - Build:
> 219][SQL]Database engine or client library specific error encountered.
>     DBMS error code: 1
>     DBMS message: Null statement result in SQLFetch.
>     Suggestion: Please see the specific database's vendor supplied
> manual(s) for further information concerning this error.
>
> >From my ODBC log:
>
> STATEMENT ERROR: func=SQLFetch, desc='', errnum=3, errmsg='Null statement
> result in SQLFetch.'
>                  ------------------------------------------------------------
>                  hdbc=75499644, stmt=75514136, result=0
>                  manual_result=1, prepare=0, internal=0
>                  bindings=0, bindings_allocated=0
>                  parameters=0, parameters_allocated=0
>                  statement_type=-2, statement='(null)'
>                  stmt_with_params=''
>                  data_at_exec=-1, current_exec_param=-1, put_data=0
>                  currTuple=-1, current_col=-1, lobj_fd=-1
>                  maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0,
> scroll_concurrency=1
>                  cursor_name=''
>                  ----------------QResult Info -------------------------------
> CONN ERROR: func=SQLFetch, desc='', errnum=0, errmsg=''
>             ------------------------------------------------------------
>             henv=76546180, conn=75499644, status=1, num_stmts=16
>             sock=76546196, stmts=76546236, lobj_type=-999
>             ---------------- Socket Info -------------------------------
>             socket=40, reverse=0, errornumber=0, errormsg='(null)'
>             buffer_in=75505936, buffer_out=75510036
>             buffer_filled_in=2, buffer_filled_out=0, buffer_read_in=2
>
> Does anyone have any ideas what may be causing this error?  I have tried
> changing the ODBC setting to just about everything that makes sense (and
> them some that don't).  The only problems with the driver seems to be
> viewing tables.
>
> Otherwise, I *am* able to create tables using postgresqlODBC via
> dbAnywhere!  Go figure that I can create a table with dbAnywhere via ODBC,
> but I can't view a table!?
>
> Any ideas?
>
> Thanks,
> Matthew






view thread (7+ messages)  latest in thread

Message-ID: <35C8A37E.B1F41333@insightdist.com>
Permalink:  ../35C8A37E.B1F41333@insightdist.com/
Also on:    postgresql.org/message-id/35C8A37E.B1F41333@insightdist.com

 · 

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: daveh@insightdist.com, matthew@wolfepub.com
  Subject: Re: [INTERFACES] postgresODBC and Symantec dbAnywhere/Visual Cafe, broken?
  In-Reply-To: <35C8A37E.B1F41333@insightdist.com>

* 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