FoxPro 2.6 dos Giving 1105 File write error

[jnoblin]

Since late January, I am getting 1105 file write errors in several programs on different computers. Seems to be triggered by the programs waiting for extended time (several hours) for operator to make an entry into a Read statement. I am using vDos 20220501 dated 5-19-22. Using a dedicated Windows 10 computer acting as a server and all workstations are Windows 10 with hardwired network.

I have duplicated the problem on a backup server at home which is a separate physical location and network.

Once the error occurs, you cannot quit Foxpro from the command window. Have to use Task Manager to end vDos

Any help would be greatly appreciated.

Thanks,

Nob

Edit for clarity: The error occurs when the operator enters the correct entry required by the Read Statement

                       All computers have SSD drives and never hibernate.

[Jos]

Not likely, but if the error occurs at the workstations that open the involved file first, I suspect it’s caused by optimistic locking at the server.

Else the server would time-out the (file) connection due to inactivity for a too long period? You could verify that by running the program locally at the backup server.

If this doesn’t bring anything, I could send you a vDos that will show the error Windows reports. These are often more informative than those of DOS, where the generic FoxPro 1105 comes from.

Jos

[jnoblin]

Thanks for your quick reply, Jos. Sometimes the problem occurs with no data file open. The workstation is at a sub-menu waiting for input from a read statement.

This morning I received the error in just a few minutes of inactivity from a workstation using the main server. I am trying it on the backup server now as you suggested.

Please send me the vDos to show the error Windows reports.

Thanks again,
Nob