Donald Kibbey wrote:
> I'm attempting to send a compound command with the UniCommand
> object and have hit what looks like a documented limitation.
> Before I go off and rethink how I'm doing this, I thought I'd
> ask to make sure this really won't work.
> What I'm attempting is to run something like this under UniObjects.
> QSELECT CLIENT.XREF "12345" :@FM: SSELECT AR.TR BY MATTER
> WITH INVOICE = "12345"
Is there some problem with executing two UniCommands in succession? I
try to minimize the RPC calls, but if it's just two I probably wouldn't
move it up to the database server.
[not tested]
uCommand = uSession.command ("QSELECT CLIENT.XREF 12345");
uCommand.exec();
uCommand = uSession.command ("SSELECT AR.TR BY MATTER WITH INVOICE =
12345");
uCommand.exec();
(I'm not sure if UniCommands are mutable, you might be able to do
uCommand.setCommand() for the second one.) Since you're in the same
session, it should keep the active select list.
--
Wendy Smoak
Application Systems Analyst, Sr.
ASU IA Information Resources Management
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
