Icon View Incident Report

Minor Minor
Reported By: Phillip Percival
Reported On: 8/4/2004
For: Version 4.09 Build 1
# 1802 Winsock Errors Not Properly Surfacing in the EDBISAMEngineError SocketErrorCode Property

Howerver I notice when you create a EDBISAMEngineError you call WSAgetLastError to get the socket error which in all cases is getting a zero probably because the error is cleared by Winsock when the socket is closed which of course is well before TDataSession raises the 11280 exception (?)

The winsock error code would be *very* useful in debugging network problems.

Resolution Resolution
Fixed Problem on 8/4/2004 in version 4.10 build 1