There are some EEDBError for which we must get more details aubout the error. EDB_ERROR_FILEMANAGER, EDB_ERROR_CORRUPT. EDB_ERROR_SERVER, EDB_ERROR_CLIENTLOST and some others, do not deliever the exact reason for the error, but instead it returns some additional text with the code embedded. From a programmer perspective this is very, very bad, as we must parse the text to find out what realy has happened. This is realy annoying and very ugly!

So please can you add an additonal ExtendedErrorCode which contains a more detailed error code, as the OS-Errorcode. Actually I want give the user a more specific error message, which is based on the real OS Error, than the much to generic EDB error message. I dont' want report any EDB Errors directly to my users as I will translate them and this is a pain without the OS Errors.

Rolf,

<< There are some EEDBError for which we must get more details aubout the error. EDB_ERROR_FILEMANAGER, EDB_ERROR_CORRUPT. EDB_ERROR_SERVER, EDB_ERROR_CLIENTLOST and some others, do not deliever the exact reason for the error, but instead it returns some additional text with the code embedded. From a programmer perspective this is very, very bad, as we must parse the text to find out what realy has happened. This is realy annoying and very ugly! >>

There are ways to intercept any common errors (such as the EDB_ERROR_CLIENTLOST error) by using events such as the OnRemoteReconnect event, and anything else is a serious error that should be logged and handled as such.  IOW, having an extended error code isn't going to help you as much as a full error message.

Tim Young
Elevate Software
www.elevatesoft.com

Sorry but I strongly disagree here. Your are right for the connect errors but there are other errors which have system errors embedded and this ones are very ugly! In a non english application the user will see mixed language errors and this looks absolutly unprofessional for our customers and gives a bad ligth on us developers. I want be able to return my own messages in the correct language and so I need the OS code to to get that all translated correctly with OS error messages, as the Windows error code is needed to get the error message.

A such generic error like EDB_ERROR_FILEMANAGER is a pain to get the users a well formed error message, without to show them the cryptic language mixed EDB error message.

I'm very curious as you think this is not needed.

Rolf,

<< I'm very curious as you think this is not needed. >>

Because that's what I did with DBISAM, and my experiences with that tells me that it wasn't satisfactory (and that was with 10+ different attributes/properties being logged for every exception).

What you're effectively asking for is a better way of localizing the error messages, which is a similar, but different, issue.  I can certainly look into having our binaries load localized strings from a text file, etc.

Tim Young
Elevate Software
www.elevatesoft.com