>Time to start looking at common things:
>
>- Are temp files going to the local drive
>- Is the executable on the local drive or the network
>- Is the import using tables on the local drive or network
>- How is the server configured?
>- Is the server using write caching, which can cause errors
>- Is the table you are importing to being used EXCLUSIVE or SHARED during the import. If shared, what other processes are using the table?

I've found out some more information and don't know what to make of it.

When I step through the code and get the internal consistency error, and then click on the OK button for the error dialog, sometimes I get the message in the VFP session, "Unable to access selected table". The call stack shows that current program is _ri_update_csrcthdr. This is not the table I'm inserting into. There shouldn't be a trigger firing.

The relational integrity looks like this:

PARENT TABLE CHILD TABLE UPDATE DELETE INSERT TAG
CSRCTHDR CSRCTDET CASCADE CASCADE RESTRICT CBATCH
WELLS CSRCTDET CASCADE IGNORE IGNORE CWELLID
WELLS INCOME CASCADE IGNORE IGNORE CWELLID

At the time I get the error, I'm inserting into table INCOME. Why would the update trigger for CSRCTHDR fire and why would it cause an internal consistency error?

I've tried inserting into a cursor and then appending into the table. I get the same error on the append.