Thread: Writing BLOBS to pgsql via ODBC using VB
I am having problems while trying to insert a BLOB into a pgsql table using VB.
The error i get is:
S1090: [Microsoft][ODBC Driver Manager] Invalid String or buffer
length
I am using postgresql 7.1.3, Postgresql ODBC driver 7.01.00.07 and RDO 2.0
Have you any idea why i get this error?
Additional infos:
Here is the table definition:
CREATE TABLE MYTABLE (
MAIN INTEGER NOT NULL PRIMARY KEY,
OBJECT LO
);
Here is the code:
Private Sub Command1_Click()
Dim rdoConn As New rdoConnection, rdoRS As rdoResultset, SQL As String
Dim numfile As Integer
Dim filesize As Long
Dim query As rdoQuery
Dim chunk() As Byte
' DB Connection
With rdoConn
.Connect = "uid=myuser;pwd=mypwd;DSN=BLOB_TEST;"
.CursorDriver = rdUseOdbc
.LoginTimeout = 3
.EstablishConnection rdDriverNoPrompt
End With
Set query = rdoConn.CreateQuery("MyQuery", "select * from mytable")
Set rdoRS = query.OpenResultset(rdOpenKeyset, rdConcurRowVer)
If rdoRS Is Nothing Or rdoRS.Updatable = False Then
MsgBox "Cannot create rdoResultSet"
End
End If
' Now insert the record in the table
If rdoRS.EOF Then
' Insert a new record
rdoRS.AddNew
' The MAIN field
rdoRS!MAIN = 2678
' Get a file number
numfile = FreeFile
' Open the file i've to insert in the table
Open "c:\myfile.doc" For Binary Access Read As #numfile
filesize = LOF(numfile)
If filesize = 0 Then
MsgBox "Unable to open the file"
Close
End
End If
ReDim chunk(filesize)
' Read the file into the array
Get #numfile, , chunk()
' Try to insert
rdoRS!OBJECT.AppendChunk chunk()
' In the update statement i get the error
rdoRS.Update
Close #numfile
End If
End Sub
Regards,
Doct. Eng. Denis
Gasparin denis@edistar.com
---------------------------------------------------------------------------------------
Programmer & System
Administrator http://www.edistar.com
---------------------------------------------------------------------------------------
Well alas we've seen it all before
Knights in armour, days of yore
The same old fears and the same old crimes
We haven't changed since ancient times
-- Iron Hand -- Dire Straits --
---------------------------------------------------------------------------------------
I have tried the same thing also with ADO and the error is the same. Here
are some debug informations from the log of the odbc driver and the queries
issued by the postgres backend.
Why the queries needed to insert the record are not present? (nor in ODBC
neither in backend log)
If anyone have successfully inserted a record using vb, can tell me how he
have done? Apparently there is no way...
Denis
PS: If i use the "Insert OLE object" in MS Access, the insertion works...
Obviously in my application i have not to use Access...
---- ODBC LOG ----
disable_optimizer=1, ksqo=1, unique_index=1,
use_declarefetch=0
text_as_longvarchar=1, unknowns_as_longvarchar=0,
bools_as_char=1
extra_systable_prefixes='dd_;', conn_settings=''
conn=184978392, query=' '
conn=184978392, query='set DateStyle to 'ISO''
conn=184978392, query='set geqo to 'OFF''
conn=184978392, query='set ksqo to 'ON''
conn=184978392, query='select oid from pg_type where typname='lo''
[ fetched 1 rows ]
[ Large Object oid = 12937145 ]
conn=184978392, query='select version()'
[ fetched 1 rows ]
[ PostgreSQL version string = 'PostgreSQL 7.1.3 on i686-pc-linux-gnu,
compiled by GCC 2.96' ]
[ PostgreSQL version number = '7.1' ]
conn=184978392,
PGAPI_DriverConnect(out)='DSN=pgsql_test_blob;DATABASE=ctest;SERVER=10.1.2.99;PORT=5432;UID=rts;PWD=edi;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS=;FETCH=100;SOCKET=4096;UNKNOWNSIZES=0;MAXVARCHARSIZE=254;MAXLONGVARCHARSIZE=8190;DEBUG=0;COMMLOG=1;OPTIMIZER=1;KSQO=1;USEDECLAREFETCH=0;TEXTASLONGVARCHAR=1;UNKNOWNSASLONGVARCHAR=0;BOOLSASCHAR=1;PARSE=0;CANCELASFREESTMT=0;EXTRASYSTABLEPREFIXES=dd_;'
conn=184978392, query='delete from mytable'
conn=184978392, query='select * from mytable'
[ fetched 0 rows ]
conn=184978392, PGAPI_Disconnect
---- BACKEND LOG ----
Oct 22 12:46:56 clio postgres[17442]: [1] DEBUG: connection: host=xxxxxxxx
user=xxx database=test
Oct 22 12:46:56 clio postgres[17442]: [2] DEBUG: query: set DateStyle to 'ISO'
Oct 22 12:46:56 clio postgres[17442]: [3] DEBUG: ProcessUtility: set
DateStyle to 'ISO'
Oct 22 12:46:56 clio postgres[17442]: [4] DEBUG: query: set geqo to 'OFF'
Oct 22 12:46:56 clio postgres[17442]: [5] DEBUG: ProcessUtility: set geqo
to 'OFF'
Oct 22 12:46:56 clio postgres[17442]: [6] DEBUG: query: set ksqo to 'ON'
Oct 22 12:46:56 clio postgres[17442]: [7] DEBUG: ProcessUtility: set ksqo
to 'ON'
Oct 22 12:46:56 clio postgres[17442]: [8] DEBUG: query: select oid from
pg_type where typname='lo'
Oct 22 12:46:56 clio postgres[17442]: [9] DEBUG: query: select version()
Oct 22 12:46:56 clio postgres[17442]: [10] DEBUG: query: delete from myt
Oct 22 12:46:56 clio postgres[17442]: [11] DEBUG: query: select * from myt
At 19/10/01 18.20, you wrote:
>I am having problems while trying to insert a BLOB into a pgsql table
>using VB.
>The error i get is:
> S1090: [Microsoft][ODBC Driver Manager] Invalid String or buffer
> length
>
>I am using postgresql 7.1.3, Postgresql ODBC driver 7.01.00.07 and RDO 2.0
>
>Have you any idea why i get this error?
>
>
>Additional infos:
>
>Here is the table definition:
>CREATE TABLE MYTABLE (
> MAIN INTEGER NOT NULL PRIMARY KEY,
> OBJECT LO
>);
>
>Here is the code:
>
>Private Sub Command1_Click()
>
>Dim rdoConn As New rdoConnection, rdoRS As rdoResultset, SQL As String
>Dim numfile As Integer
>Dim filesize As Long
>Dim query As rdoQuery
>Dim chunk() As Byte
>
>' DB Connection
>With rdoConn
> .Connect = "uid=myuser;pwd=mypwd;DSN=BLOB_TEST;"
> .CursorDriver = rdUseOdbc
> .LoginTimeout = 3
> .EstablishConnection rdDriverNoPrompt
>End With
>Set query = rdoConn.CreateQuery("MyQuery", "select * from mytable")
>Set rdoRS = query.OpenResultset(rdOpenKeyset, rdConcurRowVer)
>If rdoRS Is Nothing Or rdoRS.Updatable = False Then
> MsgBox "Cannot create rdoResultSet"
> End
>End If
>
>' Now insert the record in the table
>If rdoRS.EOF Then
> ' Insert a new record
> rdoRS.AddNew
>
> ' The MAIN field
> rdoRS!MAIN = 2678
>
> ' Get a file number
> numfile = FreeFile
>
> ' Open the file i've to insert in the table
> Open "c:\myfile.doc" For Binary Access Read As #numfile
> filesize = LOF(numfile)
> If filesize = 0 Then
> MsgBox "Unable to open the file"
> Close
> End
> End If
>
> ReDim chunk(filesize)
>
> ' Read the file into the array
> Get #numfile, , chunk()
>
> ' Try to insert
> rdoRS!OBJECT.AppendChunk chunk()
>
> ' In the update statement i get the error
> rdoRS.Update
> Close #numfile
> End If
>End Sub
>
>
>Regards,
>
>
>Doct. Eng. Denis
>Gasparin denis@edistar.com
>---------------------------------------------------------------------------------------
>Programmer & System
>Administrator http://www.edistar.com
>---------------------------------------------------------------------------------------
> Well alas we've seen it all before
> Knights in armour, days of yore
> The same old fears and the same old crimes
> We haven't changed since ancient times
>
> -- Iron Hand -- Dire Straits --
>---------------------------------------------------------------------------------------
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
Denis Gasparin wrote: > > I have tried the same thing also with ADO and the error is the same. Are you setting the CursorLocation memeber as adUseClient ? regards, Hiroshi Inoue
> Are you setting the CursorLocation memeber as adUseClient ?
>
>regards,
>Hiroshi Inoue
Ok, it worked. I think that it would be great to insert that tip in the faq
at the odbc.postgresql.org.
Now another question:
is there possible to use lo with parameterized queries (ADO command object)?
I have tried but i receive a query error. It seems like the odbc driver
doesn't use the lo interface but tryies to insert the record into the db as
if the field was of bytea type (Sorry for the poor English...I hope it is
clear what i'm saying...)
At the end of the mail there is the code and the log of the odbc pgsql driver.
The table is the same of the other mail: two fields, main (of type integer)
and object (of type lo)
Thank for your help,
Denis
--- DEBUG INFORMATIONS ---
At the end of the mail there is the pgsql odbc driver log. Here instead
there is the code:
Dim cn As New ADODB.Connection
Dim rs As ADODB.Recordset
Dim cmd As ADODB.Command
Dim chunk() As Byte
Dim fd As Integer
Dim flen As Long
Dim chunks As Integer
Dim fragment As Integer
Dim main As ADODB.Parameter
Dim object As ADODB.Parameter
Dim i As Long
With cn
.ConnectionString = "dsn=pgsql_test_blob;"
.Open
.CursorLocation = adUseClient
End With
Set cmd = New ADODB.Command
With cmd
.CommandText = "delete from myt1"
.ActiveConnection = cn
.Execute
End With
Set cmd = Nothing
Set cmd = New ADODB.Command
cmd.ActiveConnection = cn
cmd.CommandText = "insert into myt1(main,object) values(?,?)"
cmd.CommandType = adCmdText
' Set the main parameter
Set main = cmd.CreateParameter("main", adInteger, adParamInput)
main.Value = 1234
Set object = cmd.CreateParameter("object", adLongVarBinary, adParamInput)
fd = FreeFile
Open "mydocument" For Binary Access Read As fd
flen = LOF(fd)
If flen = 0 Then
Close
MsgBox "Error while opening the file"
End
End If
ReDim chunk(flen)
Get fd, , chunk()
' Now insert into the parameter
object.AppendChunk chunk()
' Execute the insert command
Set rs = cmd.Execute(, Array(main, object))
cn.Close
Close
------------------------- ODBC DRIVER LOG ---------------------------------
conn=63909392, PGAPI_DriverConnect( in)='DSN=pgsql_test_blob;',
fDriverCompletion=0
DSN info:
DSN='pgsql_test_blob',server='ADDRESS',port='5432',dbase='ctest',user='myuser',passwd='mypasswd'
onlyread='0',protocol='6.4',showoid='0',fakeoidindex='0',showsystable='0'
conn_settings=''
translation_dll='',translation_option=''
Global Options: Version='07.01.0007', fetch=100, socket=4096,
unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=8190
disable_optimizer=1, ksqo=1, unique_index=1,
use_declarefetch=1
text_as_longvarchar=1, unknowns_as_longvarchar=0,
bools_as_char=1
extra_systable_prefixes='dd_;', conn_settings=''
conn=63909392, query=' '
conn=63909392, query='set DateStyle to 'ISO''
conn=63909392, query='set geqo to 'OFF''
conn=63909392, query='set ksqo to 'ON''
conn=63909392, query='BEGIN'
conn=63909392, query='declare SQL_CUR03D00B40 cursor for select oid from
pg_type where typname='lo''
conn=63909392, query='fetch 100 in SQL_CUR03D00B40'
[ fetched 1 rows ]
[ Large Object oid = 12937145 ]
conn=63909392, query='close SQL_CUR03D00B40'
conn=63909392, query='END'
conn=63909392, query='BEGIN'
conn=63909392, query='declare SQL_CUR03D00760 cursor for select version()'
conn=63909392, query='fetch 100 in SQL_CUR03D00760'
[ fetched 1 rows ]
[ PostgreSQL version string = 'PostgreSQL 7.1.2 on i686-pc-linux-gnu,
compiled by GCC 2.96' ]
[ PostgreSQL version number = '7.1' ]
conn=63909392, query='close SQL_CUR03D00760'
conn=63909392, query='END'
conn=63909392,
PGAPI_DriverConnect(out)='DSN=pgsql_test_blob;DATABASE=ctest;SERVER=10.1.2.99;PORT=5432;UID=rts;PWD=edi;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS=;FETCH=100;SOCKET=4096;UNKNOWNSIZES=0;MAXVARCHARSIZE=254;MAXLONGVARCHARSIZE=8190;DEBUG=0;COMMLOG=1;OPTIMIZER=1;KSQO=1;USEDECLAREFETCH=1;TEXTASLONGVARCHAR=1;UNKNOWNSASLONGVARCHAR=0;BOOLSASCHAR=1;PARSE=0;CANCELASFREESTMT=0;EXTRASYSTABLEPREFIXES=dd_;'
conn=63909392, query='delete from myt1'
conn=63909392, query='insert into myt1(main,object)
values(1234,'\\320\\317\\021\\340\\241\\261\\032\\341\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\076\\000\\003\\000\\376\\377\\011\\000\\006\\000\\00.....
OTHER DATA')'
ERROR from backend during send_query: 'ERROR: lo_in: error in parsing
"\320\317\021\340\241\261\032\341\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\076\000\003\000\376\377\011\000\006\000\000\000\000\000\000\000\000\00\002\000\000\324Y\000\000\372\000\000\000\013U\000\000\025\000\000\000\000\000\000\0
................ OTHER DATA ...........................
00\000\000\140\046\000\000\000\000\000\000\140\046\000\000\000\000\000\000\140\046\000\000\000\000\000\000\140\046\000\000\000\000\000\000\013U\000\000\000\000\000\000\044\051\000\000
\000\000\000\000\274\037\000\000\000\0'
STATEMENT ERROR: func=SC_execute, desc='', errnum=7, errmsg='Error while
executing the query'
------------------------------------------------------------
hdbc=63909392, stmt=63966672, result=63972640
manual_result=0, prepare=0, internal=0
bindings=0, bindings_allocated=0
parameters=63972496, parameters_allocated=2
statement_type=1, statement='insert into
myt1(main,object) values(?,?)'
stmt_with_params='insert into myt1(main,object)
values(1234,'\\320\\317\\021\\340\\241\\261\\032\\341\\000\\000\\000\\000\\000\\000\
............................ OTHER DATA ........................')'
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='SQL_CUR03D00DD0'
----------------QResult Info -------------------------------
fields=63972720, manual_tuples=0, backend_tuples=0,
tupleField=0, conn=0
fetch_count=0, fcount=0, num_fields=0, cursor='(NULL)'
message='(NULL)', command='(NULL)', notice='(NULL)'
status=7, inTuples=0
CONN ERROR: func=SC_execute, desc='', errnum=110, errmsg='ERROR: lo_in:
error in parsing
"\320\317\021\340\241\261\032\341\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\076\000\003\000\376\377\011\000\006\000\000\000\000\000\000\000\000\000\000\000\001\000\000\000n\000\000\000\000
..................... OTHER DATA ............................
00\000\000\013U\000\000\000\000\000\000\044\051\000\000\000\000\000\000\274\037\000\000\000\0'
------------------------------------------------------------
henv=63964800, conn=63909392, status=1, num_stmts=16
sock=63964816, stmts=63964864, lobj_type=12937145
---------------- Socket Info -------------------------------
socket=488, reverse=0, errornumber=0, errormsg='(NULL)'
buffer_in=63920280, buffer_out=63924384
buffer_filled_in=3743, buffer_filled_out=0, buffer_read_in=3743
conn=63909392, PGAPI_Disconnect
How about the following ?
Denis Gasparin wrote:
>
> > Are you setting the CursorLocation memeber as adUseClient ?
> >
> >regards,
> >Hiroshi Inoue
>
> Ok, it worked. I think that it would be great to insert that tip in the faq
> at the odbc.postgresql.org.
>
> Now another question:
> is there possible to use lo with parameterized queries (ADO command object)?
> I have tried but i receive a query error. It seems like the odbc driver
> doesn't use the lo interface but tryies to insert the record into the db as
> if the field was of bytea type (Sorry for the poor English...I hope it is
> clear what i'm saying...)
>
> At the end of the mail there is the code and the log of the odbc pgsql driver.
> The table is the same of the other mail: two fields, main (of type integer)
> and object (of type lo)
>
> Thank for your help,
>
> Denis
>
> --- DEBUG INFORMATIONS ---
> At the end of the mail there is the pgsql odbc driver log. Here instead
> there is the code:
>
> Dim cn As New ADODB.Connection
> Dim rs As ADODB.Recordset
> Dim cmd As ADODB.Command
> Dim chunk() As Byte
> Dim fd As Integer
> Dim flen As Long
> Dim chunks As Integer
> Dim fragment As Integer
> Dim main As ADODB.Parameter
> Dim object As ADODB.Parameter
> Dim i As Long
>
> With cn
> .ConnectionString = "dsn=pgsql_test_blob;"
> .Open
> .CursorLocation = adUseClient
> End With
>
> Set cmd = New ADODB.Command
> With cmd
> .CommandText = "delete from myt1"
> .ActiveConnection = cn
> .Execute
> End With
>
> Set cmd = Nothing
>
> Set cmd = New ADODB.Command
> cmd.ActiveConnection = cn
> cmd.CommandText = "insert into myt1(main,object) values(?,?)"
> cmd.CommandType = adCmdText
>
> ' Set the main parameter
> Set main = cmd.CreateParameter("main", adInteger, adParamInput)
> main.Value = 1234
' add the following
cmd.Parameters.Append main
>
> Set object = cmd.CreateParameter("object", adLongVarBinary,
adParamInput)
' change as follows(100000 should be large enough)
Set object = cmd.CreateParameter("object", adLongVarBinary,
adParamInput, 100000)
' add the following
cmd.Parameters.Append object
> fd = FreeFile
> Open "mydocument" For Binary Access Read As fd
> flen = LOF(fd)
> If flen = 0 Then
> Close
> MsgBox "Error while opening the file"
> End
> End If
> ReDim chunk(flen)
> Get fd, , chunk()
> ' Now insert into the parameter
> object.AppendChunk chunk()
>
> ' Execute the insert command
> Set rs = cmd.Execute(, Array(main, object))
' Change as follows
Set rs = cmd.Execute
> cn.Close
> Close
>
Ok, it worked again...
Thank you very much for your help.
If i write a little document about visual basic, ADO and LO object can I
post to you or to the mailing list? I think this will help all those
persons (like me) that are forced to use M$ products or windows based
software...
Denis
At 24/10/01 08.05, Hiroshi Inoue wrote:
>How about the following ?
>
>Denis Gasparin wrote:
> >
> > > Are you setting the CursorLocation memeber as adUseClient ?
> > >
> > >regards,
> > >Hiroshi Inoue
> >
> > Ok, it worked. I think that it would be great to insert that tip in the faq
> > at the odbc.postgresql.org.
> >
> > Now another question:
> > is there possible to use lo with parameterized queries (ADO command
> object)?
> > I have tried but i receive a query error. It seems like the odbc driver
> > doesn't use the lo interface but tryies to insert the record into the db as
> > if the field was of bytea type (Sorry for the poor English...I hope it is
> > clear what i'm saying...)
> >
> > At the end of the mail there is the code and the log of the odbc pgsql
> driver.
> > The table is the same of the other mail: two fields, main (of type integer)
> > and object (of type lo)
> >
> > Thank for your help,
> >
> > Denis
> >
> > --- DEBUG INFORMATIONS ---
> > At the end of the mail there is the pgsql odbc driver log. Here instead
> > there is the code:
> >
> > Dim cn As New ADODB.Connection
> > Dim rs As ADODB.Recordset
> > Dim cmd As ADODB.Command
> > Dim chunk() As Byte
> > Dim fd As Integer
> > Dim flen As Long
> > Dim chunks As Integer
> > Dim fragment As Integer
> > Dim main As ADODB.Parameter
> > Dim object As ADODB.Parameter
> > Dim i As Long
> >
> > With cn
> > .ConnectionString = "dsn=pgsql_test_blob;"
> > .Open
> > .CursorLocation = adUseClient
> > End With
> >
> > Set cmd = New ADODB.Command
> > With cmd
> > .CommandText = "delete from myt1"
> > .ActiveConnection = cn
> > .Execute
> > End With
> >
> > Set cmd = Nothing
> >
> > Set cmd = New ADODB.Command
> > cmd.ActiveConnection = cn
> > cmd.CommandText = "insert into myt1(main,object) values(?,?)"
> > cmd.CommandType = adCmdText
> >
> > ' Set the main parameter
> > Set main = cmd.CreateParameter("main", adInteger, adParamInput)
> > main.Value = 1234
>' add the following
> cmd.Parameters.Append main
>
> >
> > Set object = cmd.CreateParameter("object", adLongVarBinary,
>adParamInput)
>
>' change as follows(100000 should be large enough)
>Set object = cmd.CreateParameter("object", adLongVarBinary,
>adParamInput, 100000)
>' add the following
>cmd.Parameters.Append object
>
> > fd = FreeFile
> > Open "mydocument" For Binary Access Read As fd
> > flen = LOF(fd)
> > If flen = 0 Then
> > Close
> > MsgBox "Error while opening the file"
> > End
> > End If
> > ReDim chunk(flen)
> > Get fd, , chunk()
> > ' Now insert into the parameter
> > object.AppendChunk chunk()
> >
> > ' Execute the insert command
> > Set rs = cmd.Execute(, Array(main, object))
>
>' Change as follows
>Set rs = cmd.Execute
>
> > cn.Close
> > Close
> >
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
> -----Original Message----- > From: Denis Gasparin [mailto:denis@edinet.it] > > Ok, it worked again... > Thank you very much for your help. > > If i write a little document about visual basic, ADO and LO object can I > post to you or to the mailing list? I think this will help all those > persons (like me) that are forced to use M$ products or windows based > software... OK please send it to me. Probably I could insert it into the faq. regards, Hiroshi Inoue
> -----Original Message----- > From: Hiroshi Inoue [mailto:Inoue@tpf.co.jp] > Sent: 24 October 2001 16:23 > To: Denis Gasparin > Cc: pgsql-odbc@postgresql.org > Subject: Re: [ODBC] Writing BLOBS to pgsql via ODBC using VB > > > > -----Original Message----- > > From: Denis Gasparin [mailto:denis@edinet.it] > > > > Ok, it worked again... > > Thank you very much for your help. > > > > If i write a little document about visual basic, ADO and LO > object can > > I > > post to you or to the mailing list? I think this will help > all those > > persons (like me) that are forced to use M$ products or > windows based > > software... > > OK please send it to me. Probably I could insert it into the faq. > > regards, > Hiroshi Inoue If you can't Hiroshi, I certainly can - perhaps you could CC it to me Denis. Regards, Dave.
Dave Page wrote: > > > -----Original Message----- > > From: Hiroshi Inoue [mailto:Inoue@tpf.co.jp] > > Sent: 24 October 2001 16:23 > > To: Denis Gasparin > > Cc: pgsql-odbc@postgresql.org > > Subject: Re: [ODBC] Writing BLOBS to pgsql via ODBC using VB > > > > > > > -----Original Message----- > > > From: Denis Gasparin [mailto:denis@edinet.it] > > > > > > Ok, it worked again... > > > Thank you very much for your help. > > > > > > If i write a little document about visual basic, ADO and LO > > object can > > > I > > > post to you or to the mailing list? I think this will help > > all those > > > persons (like me) that are forced to use M$ products or > > windows based > > > software... > > > > OK please send it to me. Probably I could insert it into the faq. > > > > regards, > > Hiroshi Inoue > > If you can't Hiroshi, I certainly can - perhaps you could CC it to me Denis. Thanks Dave. Denis, please send it to Dave or send it to this list also if the document isn't that big. Dave certainly could insert it to the faq. regards, Hiroshi Inoue
I apologize for the delay... but i didn't have much time this
week-end. Now the Mini-HowTo about using Postgresql Large Objects in Visual
Basic is ready. It is example based and I think this is the best thing to
those already knowing Visual Basic db interfaces.
The document covers LO usage with ADO, RDO and DAO (the three main
db interfaces on VB).
If Dave or Hiroshi could put this document in the FAQ at the
Postgresql ODBC site, I (and all Postgresql and Visual Basic users) will
eternally grateful...
I hope it helps!
Regards,
Doct. Eng. Denis
Gasparin denis@edistar.com
---------------------------------------------------------------------------------------
Programmer & System
Administrator http://www.edistar.com
---------------------------------------------------------------------------------------
Well alas we've seen it all before
Knights in armour, days of yore
The same old fears and the same old crimes
We haven't changed since ancient times
-- Iron Hand -- Dire Straits --
---------------------------------------------------------------------------------------
At 25/10/01 00.47, you wrote:
>Dave Page wrote:
> >
> > > -----Original Message-----
> > > From: Hiroshi Inoue [mailto:Inoue@tpf.co.jp]
> > > Sent: 24 October 2001 16:23
> > > To: Denis Gasparin
> > > Cc: pgsql-odbc@postgresql.org
> > > Subject: Re: [ODBC] Writing BLOBS to pgsql via ODBC using VB
> > >
> > >
> > > > -----Original Message-----
> > > > From: Denis Gasparin [mailto:denis@edinet.it]
> > > >
> > > > Ok, it worked again...
> > > > Thank you very much for your help.
> > > >
> > > > If i write a little document about visual basic, ADO and LO
> > > object can
> > > > I
> > > > post to you or to the mailing list? I think this will help
> > > all those
> > > > persons (like me) that are forced to use M$ products or
> > > windows based
> > > > software...
> > >
> > > OK please send it to me. Probably I could insert it into the faq.
> > >
> > > regards,
> > > Hiroshi Inoue
> >
> > If you can't Hiroshi, I certainly can - perhaps you could CC it to me
> Denis.
>
>Thanks Dave. Denis, please send it to Dave or send it to this
>list also if the document isn't that big. Dave certainly could
>insert it to the faq.
>
>regards,
>Hiroshi Inoue