Description of problem:
When a record is inserted in a table that is accessed through ODBC and has a
primary key in it, if the PK is not filled in by the user oobase crashes.

Version-Release number of selected component (if applicable):
On a Fedora Core 4 system with the following versions:
postgresql-odbc-08.00.0100-1
unixODBC-2.2.11-3.FC4.1
qt-ODBC-3.3.4-15.4 
unixODBC-kde-2.2.11-3.FC4.1 
openoffice.org-core-2.0.1.1-5.1
postgresql-8.0.7-1.FC4.1


How reproducible:
Always

Steps to Reproduce:
Begin with a postgres database that has a single table (ptab).
The table has three fields, setup as follows:
CREATE TABLE ptab (
    tadtest_id integer DEFAULT nextval('"ptab_tadtest_id_seq"'::text) NOT NULL,
    tadtest character varying(50),
    tadsecitem character varying(15)
);
tadtest_id is a SEQUENCEd number.
[I attached the following on the OOo bugzilla:
 a dump and script to load the database, .odbc.ini, and the
testingdb.odb I used. Also included my firstInsert.txt and
secondInsert.txt crash info files]

ODBC is setup with a .odbc.ini.


Method for problem replication:
1) oobase ~/testingdb.odb> firstInsert.txt 2>&1
2) select Tables
3) double click ptab
4) click in tadtest field
5) type "test"
6) press tab
7) type "test"
8) press enter
9) capture crash info.
10) oobase ~/testingdb.odb> secondInsert.txt 2>&1
11) click "start recovery"
12) select Tables
13) double click ptab
14) click in tadtest field for a new record (i.e. create record 2)
15) do steps 5-9 again
  
Actual results:
Crash

Expected results:
Be ready to work on the next record.

Additional info:
See files inserted in to the OOo bugzilla.