Oh, Wise Ones!
I have a table with inventory items keyed by the itemID (longint) (7000
records) and another table with inventory transactions keyed by a unique
session and sequence pair of long integers (1.2 million records). The
transaction table also has a secondary index on the itemID and a timestamp
field (descending). Both tables 32k blocks. (Table size about 83 Mbytes,
secondary index file sizes about 30 Mbytes)
P7/32 with update 4, 3-Win2K clustered servers running Citrix with 30 - 60
users writing to one or more clustered Win 2K file servers.
Worked for months without complaint until last week. No changes to the form
or the tables (other than growing larger). Once a users passed a point in
the ItemMast table they would get a Stack Overflow error and the pdox
session would terminate. There is no explicit code that happens between
these tables as the user moves from one record to the next in the inventory
If I restructure the Transaction table, the form works fine until the next
transaction is added. I have noticed on the Win2K file server that the
Transaction table, the primary key and secondary key file date/times have
varied by as much as 22 minutes. I would expect them to be virtually the
same. Network wonks claim writeback caching is disabled.
Chimney Sweep reports no problems with the table.
TableRepair indicates the table needs repair w/o any reason showing but
error 53, level 2 "Btree record mismatch Block 1, record 9 to block 10" but
the form still works.
without repair, Chimney Sweep still reports no problems with the table.
Any ideas appreciated as always.