I have code with the format such as: COMPUTE v_cost_reg AS SUM cost_reg, + v_cost_ot AS SUM cost_ot, + v_cost_2times AS SUM cost_2times, + v_hr_reg AS SUM hr_reg, + v_hr_ot AS SUM hr_ot, + v_hr_2times AS SUM hr_2times + FROM fwo_proc_labor
I seem to remember a discussion that indicated that the COMPUTE command is not standard SQL whereas the SELECT command is. Is there a potential future problem using COMPUTE command instead of SELECT? Such as: SELECT SUM(cost_reg), + SUM(cost_ot), + SUM(cost_2times), + SUM(hr_reg), + SUM(hr_ot), + SUM(hr_2times) + INTO v_cost_reg INDICATOR vind1, + v_cost_ot INDICATOR vind2, + v_cost_2times INDICATOR vind3, + v_hr_reg INDICATOR vind4, + v_hr_ot INDICATOR vind5, + v_hr_2times INDICATOR vind6 + FROM fwo_proc_labor I now routinely use SELECT, but I am wondering if there is a need to convert the old code from COMPUTE to SELECT...any thoughts? Javier, Javier Valencia 913-915-3137 --- RBASE-L ================================================ TO POST A MESSAGE TO ALL MEMBERS: Send a plain text email to [email protected] (Don't use any of these words as your Subject: INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH, REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP) ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: INTRO ================================================ TO UNSUBSCRIBE: Send a plain text email to [email protected] In the message SUBJECT, put just one word: UNSUBSCRIBE ================================================ TO SEARCH ARCHIVES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: SEARCH-n (where n is the number of days). In the message body, place any text to search for. ================================================
