We are retrieving errors in the folowing case:

An application on a workstation opens a table and it inserts a record to
that table. On creation of the record a query is executed which determines
the maximum key-value of the existing records. We add one to the result
value of the query and we use this value as the key-value of the new record.

The same application on an other workstation opens the same table and it
inserts also a record while the state of the table on the first workstation
is still in insert-mode.

So the key-value of the new records on both workstations are the same. When
we post one of the records the record will be posted with the mentioned
key-value. When we post the other record the application adds one to the
key-value before the record is posted.

During this process we don't get any errors but when we examinate the table
we have been used we always have index-errors on that table when we use an
NT-server.

But when we put the database on a windows 98 configuration we do NOT have
this problem.

Configuration:

Application written in Delphi 4.0 pro
Paradox database (The problem table has several indexes, Primary Key + 21
Sec. Keys)
Windows 98 as workstations (2 workstations)
Windows NT 4.0 (Build 1381 service pack 3) as server

There's a simple way round this. You need a separate table with a
single field to hold the last key value used. When a user inserts a
new record, in the OnNewRecord event, open this table and try to set
Exclusive to True. If successful, get the current value, increment it
and post it back to the single-field table. Then use that value as the
key for the new record.

I'm not sure I've explained that very clearly, so if it doesn't make
sense mail me and I'll try to explain better.

--
Stephen Brown

NT has a bug with IPX/SPX prior to Service Pack 4.

HTH,

Paul Motyer
SoftStuff
PO Box 637, Croydon, VIC, Australia, 3136

ftAutoInc ???