RE: Strange QtmhCvtDB problem

I had this same problem in June, I think.  The collective group response (I
think this list) was not to use this api but to use the cgi parse api
instead.  The parms were correct before the call to the api and wrong when
it returned.  When the ext. ds was short, it worked fine.

Phil

->-----Original Message-----
->From: web400-admin@midrange.com [mailto:web400-admin@midrange.com]On
->Behalf Of Buck Calabro
->Sent: Monday, August 05, 2002 1:52 PM
->To: web400@midrange.com
->Subject: RE: [WEB400] Strange QtmhCvtDB problem
->
->
->>If the first time it is called it works
->>correctly, then I've had this problem when
->>using named AG's.
->
->This sounds like corrupted memory.  Check to see that all parms match
->between caller and callee - not just the 'failing' one, but ALL of the
->call/callp situations.  Also look for manipulating varying length strings
->past the end of their declared length, like move *blanks to a
->varying length
->field in a subprocedure.
->
->Put a watch on the variable and see when it gets changed.
->  --buck
->_______________________________________________
->