From: Adam Lang <aalang@rutgersinsurance.com>
To: Sanjay Arora <sk@pobox.com>
Cc: pgsql-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: Large Objects...ODBC/VB6/ADO...& PostgreSQL
Date: Mon, 27 Nov 2000 10:09:26 -0500
Message-ID: <01d601c05884$08a48160$330a0a0a@6014cwpza006> (raw)
References: <200011211604.VAA07132@tcs.com>
<1948.974826605@sss.pgh.pa.us>
<200011231750.XAA07474@tcs.com>
First, try upgrading to ADO 2.5 There was an error like that for MS SQL
that was fixed in the 2.5 version.
Also, why are you using JET? You should use the OLE DB provider for ODBC.
By using JET, you are adding another level of abstraction that you don't
need.
As for using Shpe, I never have, so I can't help much there, but what I
would recommend then is trying your code without shape and see if you still
get connection problems. That way you can see if it is shape or not that is
causing it.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Sanjay Arora" <sk@pobox.com>
To: "Adam Lang" <aalang@rutgersinsurance.com>
Sent: Thursday, November 23, 2000 6:24 PM
Subject: Re: [INTERFACES] Large Objects...ODBC/VB6/ADO...& PostgreSQL
At 07:05 PM 11/21/00 , you wrote:
>What version of ADO are you using?
>
>Adam Lang
>Systems Engineer
>Rutgers Casualty Insurance Company
ADO Ver 2.1, postgreSQL 7.0.3 on RH Linux 6.2, ODBC 6.50, Visual Basic 6,
Win NT SP3 client
Seems I can't reproduce that catastrophic failure error...came quite a few
times.....am working on it....took the update out of transactions and the
catastrophic failure stopped but by then other changes were also there in
the project....can I take a raincheck ? ;-((
Another prob, if you can help me...
' Shape Query Creating Trouble
getting error "parser cannot understand near or after shape"......is this
due to MS extensions in the shape data control & should I chuck it out or is
there a byepass?
strShape = "SHAPE ( SHAPE {SELECT Act_Id FROM `TbAccountMaster` Where Act_Id
IN (" & mCodes & ") And Act_Specification <> 'CASH'} AS Command2 APPEND
({SELECT Transaction_Date AS VOUCHER_DATE,iif(Transaction_Table =
4,iif(Entry_Id <> '" & GetOpeningId & "','JOURNAL ENTRY','YEAR
OPENINGS'),'BY CASH A/C') AS PARTICULARS,iif(DRCR =
'DR',Transaction_Amount,' ')AS DEBIT,iif(DRCR = 'CR',Transaction_Amount,' ')
AS CREDIT,DRCR,Account_Code AS BALANCES ,Entry_Id FROM `TbAccountTransact`
ORDER BY Transaction_Date,Entry_Id,DRCR} AS Command1 RELATE 'Act_Id' TO
'BALANCES') AS Command1) COMPUTE Command2 BY Act_Id"
If conTmp.State = adStateClosed Then
With conTmp
.Provider = "MSDataShape.1"
Select Case Command()
Case "access"
.Open "Data Source=" & sDbPath & ";Data
Provider=Microsoft.Jet.OLEDB.4.0"
Case "postgres"
.Open conAct.ConnectionString
End Select
End With
End If
If rsTmp.State = adStateOpen Then
rsTmp.Requery
Else
With rsTmp
Set .ActiveConnection = conTmp
.CursorLocation = adUseClient
.CursorType = adOpenStatic
.LockType = adLockOptimistic
.Source = strShape
----> .Open (Error happening here)
End With
End If
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: aalang@rutgersinsurance.com, sk@pobox.com
Subject: Re: Large Objects...ODBC/VB6/ADO...& PostgreSQL
In-Reply-To: <01d601c05884$08a48160$330a0a0a@6014cwpza006>
* 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