> project.dbScholl.Execute StrSql2 , , adCmdText
First, test the SQL statement in something like the SQL window of pgAdmin.
Then
Is dbScholl a database object (like DAO) or an ADODB.Connection object?
You should understand the difference and select one.
Presuming that you really want ADO,
Are you using liked tables? ..
If so then use something like
CurrentProject.Connection.Execute StrSql2
If not linked tables then use something like
Dim cnn as new ADODB.Connection
cnn.Open "DSN=my_dbs_dsn_name" 'or a full PostgreSQL connection string to save a trip to the registry
cnn.Execute StrSql2
Tim Clarke wrote:
> To debug this sort of issue, take VB out of the picture: once it has
> processed the line creating StrSql2 for you, run the SQL directly in
> Postgres via some other method (we use pgAdmin) and make sure that code
> is OK. Then you'll know whether this is a VB or a Postgres issue.
>
> Tim Clarke
>
> -----Original Message-----
> From: dodol garut [mailto:jangkaru80@yahoo.com]
> Sent: 07 March 2006 15:24
> To: Tim Clarke
> Subject: Re: [ODBC] Postgre and Visual Basic
>
>
> When I insert a reccord from my form in VB, there was an error message
> "no columns defined in rowset"
>
> and here is my query to insert that reccord:
> dim StrSql2 as string
> StrSql2 = "insert into produk(kodeproduk,namaproduk,hargasatuan)
> values('" & text1.Text & "','" & Text2.Text & "'," & Text3.Text & ");"
>
> project.dbScholl.Execute StrSql2 , , adCmdText
>
> thanx before...
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly