A high volume application that has been running carefree for over 15 years crashed recently with this command:

DELETE FROM billing where inv_date = @invdate

It ran under VFP for10 years and was converted to .NET several years ago but the command was exactly the same under both modes.

The error was that the command was timing out.

This table has been growing steadily over the past 15 years and contains several million rows.

The SQL server timeout setting was set to no limit but research told me that .NET has its own limits and that the shorter one governs.
This change in .NET solved the issue:
this.oCommand.CommandTimeout = 60;

Is there a similar setting for VFP?