In single user, normal, when two or three people at the same time operation, is reported to the RunTime error, pop up a dialog box to debug,
Environment is: 2003 server and pb11.5

CodePudding user response:

Try to use the try first... Catch the runtime Error that wrapped up, the Error information capture to see,

CodePudding user response:

Also use the TRY... The CATCH, but cannot capture the error,

CodePudding user response:

What error object are captured?

CodePudding user response:

Only to the ws soapconnect object to the line to catch, when multiuser concurrent error, let the debugger, and normal when a single user

CodePudding user response:

Can reissue a test with WS, method is simple, and see if it has the same problem,

CodePudding user response:

Very simple no problem, with the help of data compression, among this call the DLL other developers

CodePudding user response:

Then you can block code step by step, and then test, know to find out the source of the problem

CodePudding user response:

Other personnel development of DLL should not be so harsh,

CodePudding user response:

Call resources not release?