Problem inserting with remote views in vfp

I'm in the process of converting a Visual FoxPro application from using local
tables to using a postgresql backend on a Debian box with psqlODBC on Windows
Xp.

I've set up the database server with the necessary tables containing test data
and using a remote view in VFP I can browse and update data. However when I
insert a row into the view and try to commit the change to the server I get
an error message saying that the null value for the primary key conflicts
with the non-null constraint, however the data that I am inserting is
non-null for the primary key.

Any help would be appreciated as I've run out of ideas on how to fix this.

--
Geoff Registered Linux user 196308

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Re: Problem inserting with remote views in vfp

I recommend that you turn logging on either on the ODBC side or on the serv=
er side, and see exactly what you are sending as a query.
Also, try to send the exact query you would be making from your applicatio =
via PSQL or pgAdmin and see the results.
Browsing a table is not fgoing to trigger a constraint. This will happen o=
nly if you are inserting/updating/deleting rows.


-----Original Message-----
From: pgsql-odbc-owner@postgresql.org
[mailto:pgsql-odbc-owner@postgresql.org]On Behalf Of Geoffrey Clements
Sent: Friday, April 21, 2006 3:29 PM
To: pgsql-odbc@postgresql.org
Subject: [ODBC] Problem inserting with remote views in vfp


I'm in the process of converting a Visual FoxPro application from using loc=
al=20
tables to using a postgresql backend on a Debian box with psqlODBC on Windo=
ws=20
Xp.

I've set up the database server with the necessary tables containing test d=
ata=20
and using a remote view in VFP I can browse and update data. However when =
I=20
insert a row into the view and try to commit the change to the server I get=
=20
an error message saying that the null value for the primary key conflicts=
=20
with the non-null constraint, however the data that I am inserting is=20
non-null for the primary key.

Any help would be appreciated as I've run out of ideas on how to fix this.

--=20
Geoff Registered Linux user 196308

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

---------------------------(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