Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Hello,
following situation: I open database "localdatabase" with dbaccess and
execute the following procedure:
PROCEDURE f_test (p_1 INTEGER) RETURNING INTEGER;
DEFINE l_error;
CALL remotedatabase@remoteserver:f_test(p_1) RETURNING l_error;
RETURN l_error;
END PROCEDURE;
which gives the following error:
206: The specified table (invekos.t_fmass) is not in the database.
111: ISAM error: no record found
the table invekos.t_fmass is of course not defined in "localdatabase"
but in "remotedatabase". I tought that if i call a procedure on a
remote database server, the procedure is executed in the context of
the remote database (implicitly changing connection to remote server)?
Is this not true.
Trying the same with ESQL/C works of course. An ESQL/C program with
default connection to "localdatabase" will process the call to f_test
on the remotedatabase server without any problems.
Greetins, Joerg
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.