I don't know VB very well, but I'm guessing that you can't update a
recordset that's the product of a SELECT. In any case, it's certainly
not a PostgreSQL bug. If you need more help, try pgsql-general.
On Jul 28, 2006, at 11:54 PM, Jonas Bruhn wrote:
The following bug has been logged online:
Bug reference: 2555
Logged by: Jonas Bruhn
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Windows 2000 Pro
Description: runtime error 80040e21
Details:
I'm using VB6, and trying to update a table. It is all happening on
my home
pc with IIS running too. I can download the table to a datagrid,
bit I can't
type any text i a textbox and update it whith out the error
occuring. Here
is the code and some remarks afterwards:
Private Sub command2_click()
Dim cn As ADODB.Connection
Dim rs As ADODB.Recordset
Set cn = New ADODB.Connection
cn.Open "Provider=PostgreSQL.1;Password=***;User ID=postgres;Data
Source=localhost;Location=***" ';Extended Properties="""
Set rs = New ADODB.Recordset
rs.CursorLocation = adUseClient
rs.Open "select tilbudspris, materialer from efterkalk", cn,
adOpenKeyset, adLockOptimistic
rs.AddNew
debug here --- rs("tilbudspris").Value = Text1.Text
rs("materialer").Value = Text2.Text
rs.Update
Set rs.ActiveConnection = Nothing
Set rs = Nothing
cn.Close
Set cn = Nothing
End Sub
Remarks:
The columns in the table is set to text.
I've tried to write rs!tilbudspris and rs!materialer.
I've tried to trim(text1.text)
I've tried adopenstatic
I've tried rs.movefirst
I can't recognise where the problem should be, if it isn't a bug.
Best regards
Jonas Bruhn
---------------------------(end of
broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
--
Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED]
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
