Subject | Re: [IBO] How to stop multi language error messages? |
---|---|
Author | Paul Vinkenoog |
Post date | 2002-11-28T16:25:53Z |
Hi Arno,
the first few lines tell you that something didn't work, and what the
ISC error code is (if any). The error code means nothing to the
average user, but you, the developer, can look up what it means. But
even then, you might miss some information (e.g. from the OS) that
could drastically narrow down the search.
a 255-byte limit for cross-thread strings? And how about pointers? Or
breaking up long strings into several short strings so that the
receiving thread can concatenate them again?
Greetings,
Paul Vinkenoog
> What do you think about just passing the first line of an errorMost of the time - at least if the message comes from the FB engine -
> message to the user, would it always give a unique hint of what went
> wrong?
the first few lines tell you that something didn't work, and what the
ISC error code is (if any). The error code means nothing to the
average user, but you, the developer, can look up what it means. But
even then, you might miss some information (e.g. from the OS) that
could drastically narrow down the search.
> I'm using D4 and therefor I cannot pass/share long strings acrossThreads are not exactly my strong point, and I don't know D4. Is there
> threads.
a 255-byte limit for cross-thread strings? And how about pointers? Or
breaking up long strings into several short strings so that the
receiving thread can concatenate them again?
Greetings,
Paul Vinkenoog