Unknown error?

[Peter Lameijn]

One of my programs (which runs fine) sometimes returns an errorcode 69.
What is it? (doesn't list in the helpfile )


------------------
Peter.
mailto[email protected][email protected]</A>

[This message has been edited by Peter Lameijn (edited March 13, 2001).]

[Scott Turchin]

That's not a whole lot of info to go on, what was the program doing when it generated it?

Try this:

Function GetLastErrorDescription( ByVal ErrorCode As Long, ByVal UseLastError As Long ) Export As String
Dim sRtrnCode   As Asciiz * 256
Dim lRet        As Long
If UseLastError Then ErrorCode = GetLastError()
If ErrorCode = %ERROR_SUCCESS Then Exit Function
lRet = FormatMessage( %FORMAT_MESSAGE_FROM_SYSTEM, ByVal 0&, ErrorCode, 0&, sRtrnCode, SizeOf( sRtrnCode ), 0& )
If lRet > 0 Then Function = Left$( sRtrnCode, lRet )
End Function

------------------
Scott

[Eric Pearson]

It's probably 1) an error code that is being returned by an API call (69=ERROR_TOO_MANY_SESS, whatever that is) or 2) the result of an ERROR 69 statement.

69 is also the PB/DOS error code for "communications buffer overflow."

Any of those sound plausible?

-- Eric

------------------
Perfect Sync Development Tools
Perfect Sync Web Site
Contact Us: mailto:[email protected][email protected]</A>

[Peter Lameijn]

The error is generated in the callback function of the programs main
dialog. There aren't any API calls made there directly; however there is
some COM port activity. Although error 69 isn't in the PB/DLL errorlist,
it could be a comm-buffer overflow. I'll try to increase the comm-buffers...


------------------
Peter.
mailto[email protected][email protected]</A>

[Lance Edmonds]

This is a real error, just omitted from the doc's:

Error 69
COMM error – A communications error occurred. For example, a framing error.

------------------
Lance
PowerBASIC Support
mailto:[email protected][email protected]</A>