Thanks Larry, but the table being projected from in this case (and most often in my case) are from external ODBC databases... bringing data into Rbase. So I do not think the stored procedure would be available if I understand properly and I also would not want to slow the process down. (The root reason why I need the visual feed back!)
Thanks again.. -- Thompson Technology Consultants LaPorte, IN 46350 219-363-7441 -------------- Original message -------------- From: Lawrence Lustig <[EMAIL PROTECTED]> << So based upon what I am hearing back... no moving visual feed back to a user during such a PROJECT command is currently available? (Cursors are not an option here) >> Well, there's always a solution to everything. . . If you really, really, really need the feedback you can use a stored procedure. Include the stored procedure in your PROJECT, either on a spare column or on some other column. In the Stored Procedure code update your UI (a progress bar, or whatever). If the SP is projected into a spare column it doesn't need to take params or return a value. If it's projected into a real column, it needs to accept the column data as an argument and return the same value unchanged as the return value. This will slow down your PROJECT considerably, but it will do what you want. An alternative would be to ask for an enhancement to all SQL command called WITH MESSAGE that will periodically update the UI, or a setting to do the same thing. -- Larry
