Re: "Invalid cursor position" error when using recordsetsand text fields

From: "Brian G(dot) Huber" <brianghuber(at)yahoo(dot)com>
To: "Andrew Ayers" <aayers(at)eldocomp(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: "Invalid cursor position" error when using recordsetsand text fields
Date: 2003-11-02 22:24:03
Message-ID: 001a01c3a190$05c03130$6500a8c0@bghmobile
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Thanks Andrew - yes it is a legacy app using DAO. We are porting to
Java/JDBC. In the interim we switched the field to varchar from text.
----- Original Message -----
From: "Andrew Ayers" <aayers(at)eldocomp(dot)com>
To: "Brian Huber" <brianghuber(at)yahoo(dot)com>
Cc: <pgsql-odbc(at)postgresql(dot)org>
Sent: Wednesday, October 29, 2003 10:44 AM
Subject: Re: [ODBC] "Invalid cursor position" error when using recordsetsand
text fields

Brian Huber wrote:
> I'm using recordsets in VB to through psqlODBC
> 7.3.100 and am receiving "invalid cursor position"
> when trying to retrieve the value of text fields. I
> do not get this problem when retrieving numeric
> fields.

You don't say how you are accessing the tables, etc:

* DAO (version?)
* ADO (version?)
* Straight SQL (unlikely, given your problem)
* Something else...

Likely it is one of the first two (DAO or ADO). I can tell you that I
was experiencing that problem in a conversion of an application from
Access 97 to PG (using the ODBC drivers). At the time, my application
was using DAO, and I was running into all sorts of funky problems.
Switching to ADO solved the vast majority. If I had to do it all over
again, though - I think I would have gone for straight SQL updates.

Look through both the ODBC and GENERAL list archives - my posts and such
will be in there from earlier this year.

Andrew Ayers
Phoenix, Arizona

-- CONFIDENTIALITY NOTICE --

This message is intended for the sole use of the individual and entity to
whom it is addressed, and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. If you are not
the intended addressee, nor authorized to receive for the intended
addressee, you are hereby notified that you may not use, copy, disclose or
distribute to anyone the message or any information contained in the
message. If you have received this message in error, please immediately
advise the sender by reply email, and delete the message. Thank you.

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Brian G. Huber 2003-11-02 22:28:09 Re: "Invalid cursor position" error when using recordsets and
Previous Message todhunter 2003-11-02 07:43:54 ODBC and Power Designer