Hi Gaylen,

I can think about two issues that cauld cause such problem.
- New SET TABVALIDATE command and related functionality. By default it set to 3 which means that VFP has to lock table header after openning table in order to validate record count in the table header. I would recomend to set it to 7, assuming that SP1 is installed. It's new value documented in SP1 readme file.

- The INSERT-SQL command briefly locks table header which could create contention in case of heavy insert activity. You could set REPROCESS TO AUTO but it'll also produce system message
"Attempting to lock ... Press Escape to Cancel". Other way is to use your error handler to retry INSERT when such error is generated.

>I think the error message is messed up. It says the error was in a progam called prem_calc (I keep the calculations in a separate program so I only have to look for that code in one place) which is called from a print method of one of my forms. The error message also say refers to master.insured which is a cursor and which is created long after the prem_calc program is called. Master.insured has nothing to do with the prem_calc program.
>Exclusive is set to off.
>
>I am thinking it is an insert into the policy table that is in the prem_calc program that is causing the problem. Once the premium is calculated I insert the calculations into the policy table. I may be wrong but I wouldn't think you would get a file is in use error from a cursor that you just created.
>
>The policy table is a heavily used table and everyone was going against it as they were trying out the new system.
>