O
OctavioOlguin
Guest
Greetings.. Trying to embrace mobile, I'm starting with baby step... I have the folowing routine at procedure level, BLOCK-LEVEL ON ERROR UNDO, THROW. {bi/Paqs02.i} DEFINE INPUT PARAMETER pSucursales AS INTEGER NO-UNDO. DEFINE INPUT PARAMETER pFecha1 AS DATE NO-UNDO. DEFINE INPUT PARAMETER pFecha2 AS DATE NO-UNDO. DEFINE INPUT PARAMETER pStatus AS CHARACTER NO-UNDO. DEFINE INPUT-OUTPUT PARAMETER DATASET FOR dsPaqs. /* ******************** Preprocessor Definitions ******************** */ /* *************************** Main Block *************************** */ EMPTY TEMP-TABLE ttPaquete. FOR EACH dwPaquete NO-LOCK WHERE (dwPaquete.Sucursal = pSucursales OR pSucursales = 0) AND dwPaquete.FechaSalida = pFecha1 AND dwPaquete.FechaSalida = pFecha2 AND can-do(pStatus, dwPaquete.statusP): CREATE ttPaquete. BUFFER-COPY dwPaquete TO ttPaquete. RELEASE ttPaquete. END. meaning I call it with RUN bi/paqs02.p ON hServer (fSucursal, fFecha, fFecha-2, Flags, INPUT-OUTPUT DATASET dsPaqs). on my n-tier desktop app... Now I would like to expose it as a simple mobile app, but the part that the internal procedures are the one exposed is tricky for me still, as I can't imagine how should I transform the current process, so it is "mobilizer-friendly". Any clue would be deeply appreciated
Continue reading...
Continue reading...