Reported By: Dave Stephenson Reported On: 11/2/2001 For: Version 3.03 Build 1
# 932Remote Tracing not Reporting Trace Message Values Properly in all Cases Using a Remote Session, FReplyHeader.ResultCode does not return the appropriate error code the first time. To reproduce a visual representation of the error call TDBISAMSession.GetRemoteUser with an invalid Username. An exception is raised, but the tracemessage value comes back as DBISAM_NONE. Call GetRemoteUser again and the Tracemessage value comes back as DBISAM_REMOTENOUSER.
Comments and WorkaroundsThanks to Dave for also relaying the actual fix to us.
ResolutionFixed Problem on 11/3/2001 in version 3.04 build 1