Re: [twsocket] BgException when a tcp client application is started byanother application

Hello Francois, I found the problem by examining all the socket event handlers. You are right. It's a date time conversion function that gets an invalid environment parameter when run from another app. I think the reason madExcept didn't catch it is because BgExcept caught it? Anyway, thanks a l

Re: [twsocket] BgException when a tcp client application is started byanother application

Hello Francois, I installed madExcept, and verified it working with a divided by 0 exception I created on purpose. It was caught by madExcept. However, the problem I had in BgException didn't raise any exception that madExcept was able to catch... -- Best regards, Jack Wednesday, September 28,

Re: [twsocket] BgException when a tcp client application is started byanother application

Hello Francois, I'll try that. Any idea why it doesn't happen when it's run from Windows Explorer? -- Best regards, Jack Wednesday, September 28, 2005, 2:36:34 PM, you wrote: >> BgException: EConvertError: Invalid argument to date encode > You pass an invalid argument to some date encode fun

Re: [twsocket] BgException when a tcp client application is started byanother application

> BgException: EConvertError: Invalid argument to date encode You pass an invalid argument to some date encode function. This happend in one of your socket event hanlder since it is trapped by BgException. I suggest you use MadExcept to find where it occurs exactly. MadExcept is really an incred