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

[ psqlodbc-Bugs-1000778 ] Error 3219 - Operation is not allowed in this context - Blobs and VB6

From: <noreply(at)pgfoundry(dot)org>
To: noreply(at)pgfoundry(dot)org
Subject: [ psqlodbc-Bugs-1000778 ] Error 3219 - Operation is not allowed in this context - Blobs and VB6
Date: 2006-11-16 07:45:05
Message-ID: 20061116074505.A5F94216C58@pgfoundry.org (view raw or flat)
Thread:
Lists: pgsql-odbc
Bugs item #1000778, was opened at 2006-11-13 17:52
You can respond by visiting: 
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000778&group_id=1000125

Category: None
Group: None
>Status: Closed
Resolution: None
Priority: 3
Submitted By: Nobody (None)
>Assigned to: Hiroshi Inoue (hinoue)
Summary: Error 3219 - Operation is not allowed in this context - Blobs and VB6

Initial Comment:
I am trying to use PostgreSQL 8.1.X, but now when I try retrieve a file in lo field type, occurs the erros Error 3219 - Operation is not allowed in this context, I am using Visual Basic 6 - ADO - ODBC 8.02.02

I did this example for test.

http://gborg.postgresql.org/project/psqlodbc/genpage.php?howto-vblo

----------------------------------------------------------------------

Comment By: Nobody (None)
Date: 2006-11-14 15:10

Message:
I could to solve this problem.
This error occurs because my odbc connection was configured with
protocol 6.4 because I am used to odbc 7.03.02, for the new version
the protocol must be 7.4.
Others configuration must be change is the Driver, that must be Postgresql ANSI

My connection String
Before:

Driver=PostgreSQL};SERVER=localhost;DATABASE=db;UID=postgres;PWD=;ReadOnly=0;
  Protocol=6.4;
FakeOidIndex=0;ShowOidColumn=0;RowVersioning=0;ShowSystemTables=1;ConnSettings=;Fetch=100;Socket=4096;UnknownSizes=0;MaxVarcharSize=254;MaxLongVarcharSize=65536;Debug=0;CommLog=0;Optimizer=1;Ksqo=1;UseDeclareFetch=0;TextAsLongVarchar=1;UnknownsAsLongVarchar=0;BoolsAsChar=0;Parse=0;CancelAsFreeStmt=0;ExtraSysTablePrefixes=dd_;;LFConversion=1;UpdatableCursors=0;DisallowPremature=0;TrueIsMinus1=1;BI=-5;


After;

Driver={PostgreSQL ANSI};SERVER=localhost;PORT=5432;UID=postgres;PWD=;SSLmode=disable;ReadOnly=0;

Protocol=7.4;

FakeOidIndex=0;ShowOidColumn=0;RowVersioning=0;ShowSystemTables=0;ConnSettings=;Fetch=100;Socket=4096;UnknownSizes=0;MaxVarcharSize=254;MaxLongVarcharSize=8190;Debug=0;CommLog=0;Optimizer=1;Ksqo=1;UseDeclareFetch=0;TextAsLongVarchar=1;UnknownsAsLongVarchar=0;BoolsAsChar=1;Parse=0;CancelAsFreeStmt=0;ExtraSysTablePrefixes=dd_;;LFConversion=1;UpdatableCursors=1;DisallowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarBinary=0;UseServerSidePrepare=0;LowerCaseIdentifier=0;XaOpt=1"


----------------------------------------------------------------------

Comment By: Nobody (None)
Date: 2006-11-14 14:53

Message:
Hi Hiroshi

Yes I defined the type lo and I have been use type lo since version 7.4..

Juari

----------------------------------------------------------------------

Comment By: Hiroshi Inoue (hinoue)
Date: 2006-11-14 02:45

Message:
Hi

Did you define the type lo and use it ?

regards,
Hiroshi Inoue

----------------------------------------------------------------------

Comment By: Nobody (None)
Date: 2006-11-14 00:33

Message:
Hi, My Apologize

I was post this question and after my test, I found the solution, this error occurs because my odbc connection was configured with protocol 6.4 because I am used to odbc 7.03.02, for the new version the protocol must be 7.4.

Thanks

Juari D. Silva
Developer Coordinator

----------------------------------------------------------------------

Comment By: Hiroshi Inoue (hinoue)
Date: 2006-11-13 23:45

Message:
Hi

Did you define the type lo and use it ?

regards,
Hiroshi Inoue

----------------------------------------------------------------------

You can respond by visiting: 
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000778&group_id=1000125

pgsql-odbc by date

Next:From: Hiroshi InoueDate: 2006-11-16 14:02:07
Subject: Re: Serial columns and ADO
Previous:From: Bryce NesbittDate: 2006-11-15 03:06:34
Subject: unexpected EOF within message length word

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