Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Remote ODBC Transmission to NT server Buffer, error
Message
From
21/02/1999 02:55:34
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Client/server
Title:
Remote ODBC Transmission to NT server Buffer, error
Miscellaneous
Thread ID:
00189766
Message ID:
00189766
Views:
37
I am writing an application in VFP 5.0. I am encountering an error while remotely transmitting data. The server OS is WinNT 4.0 Service pack 3. The work station OS is WinNT 4.0. I am using a laptop to dial up and transmit data, through a fire wall (that I am unfamiliar with) to a remote server.
I am using ODBC to write from the local VFP database to the remote VFP database. I am using buffering and transactions, etc. The following error occurs on a regular basis:

System Process - Lost Delayed - Write data
The system was attempting to transfer file data from buffers to The write operation failed, and only some of the data may have been written to the file.

From the MSDN documentation, it looks like data is being written to buffers on the server, and then something gets messed up. I would like to at least contain this error, or figure out how to get it to occur less often. If you look in the documentation, under “How to Disable Network Redirector File Caching” Microsoft gives a work around, but we don’t want to disable NT caching. This error seems to pop up whenever it feels like, often after the files have been closed some time, and the connection has been closed (I thought). This makes it more difficult to trap. (I put in a couple thermometers after I close the files down to count out 2.5 minutes, and the errors usually occur within that time, but I would like to get better control of this error than that).

One thing I thought might work is to get the file handle, and use the API call to FlushFileBuffers, or somehow set the FILE_FLAG_WRITE_THROUGH flag. I tried FlushFileBuffers with the FoxPro file handle, and of course it didn’t work. I noticed that I can get hold of the ODBC filehandle but have not gone back and tried it again yet, since I assume that the API call will have a different file handle than ODBC anyway. I am still not sure how to get hold of the API file handle.

If you have any suggestions I would certainly appreciate it.

Thank you.
EMail: danielj@ryte-byte.com
"If I'm paddling so hard, how come I'm going backwards?" - Pinocchio (while the whale was swallowing him...)
Reply
Map
View

Click here to load this message in the networking platform