<< 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!) >> If you're projecting into R:Base, using a PROJECT statement on attached tables, I think the stored procedures will be available. If you're sending a command to the remote DB with SSQL, they won't be, of course.
If the problem is a slow _per record_ return time from the remote DB then the stored procedure won't actually slow you down that much. It would only slow you down a lot if you're getting back a very, very large number of records and each records is returned very quickly. Can you have the data from the other DB prepared as a CSV file? It's sometimes faster to pass through an intermediate format than deal with slow ODBC drivers from other products. R:Base sucks up CSV and ASCII files like greased lighting. -- Larry
