running application using three tier connection

[selasi]

good day i have developed an application which im struggling to run.

i have created an interface which calls the next program on click of button ok
as follows: note this is a snippet *
DO WITH FRAME fram1:
ASSIGN
ftreaty = TRIM (ptreaty:SCREEN-VALUE).
fuy = DATE (puy:SCREEN-VALUE).

END.

RUN d:\custom\rpt005.p (INPUT ptreaty,
INPUT puy).
and there is an appserver that connects to the database so i have two more programs, one that connects to the database and posts the information to a temp table and then posts the temp table infomation to another porgram which will display the data..

however when i run the program i get the following error message:"the caller's temp-table parameter temp1 does not match to the parameter temp-table temp1(5363)" i have created the same temp tables and i cant find where im going wrong.

may anyone assist me

kind regards

 

[MaximMonin]

use 1 include file for appserver layer and interface layer.
define temp-table in include.

 

[selasi]

thank you.

as a matter of fact i have one include file for appserver layer and this is what i have done


DEFINE VARIABLE hServer AS HANDLE NO-UNDO.
DEFINE INPUT PARAMETER ptreaty AS CHAR NO-UNDO.
DEFINE INPUT PARAMETER puy AS DATE NO-UNDO.
DEFINE VARIABLE wc-prog AS CHARACTER NO-UNDO INITIAL "rpt005_".
{D:\custom\appserv.i}
RUN appServerConnect(INPUT 'busObj',
INPUT ?,
INPUT ?,
OUTPUT hServer).
is there any part that i need to correct?

 

[MaximMonin]

you dont pass any temp-table in posted example. I see character type, 2 unknown values and handle.

 

[RealHeavyDude]

The code fragments you provide do not prove anything.

As matter of fact: When you are passing temp-table parameters between procedures, regardless whether they are in the same session or across the AppServer boundary, the schema definition must match in both procedure. If they don't, that's exactly the error you get.

You can try it in the same session. If it works in the same session but does not work with the AppServer, then one thing is sure: The procedure you're running on the AppServer is not the same version you're running in your development environment. You should compile both procedures and deploy it to the AppServer. If the AppServer agents are started with the -q parameter or the procedure runs persistent you even might need to restart the AppServer for it to pick up the new version.

Heavy Regards, RealHeavyDude.