Dear Tom Frederick, Your email has multiple aspects of discussion, below are my suggestions as per my experience on R:Base which may be beneficial to you.
- first of all, to avoid conflicts b/w users u did right by converting ur tables, created by project command to the Temp tables becoz temp tables are only available to the local user. - I don't have the idea why u r using temp views, if u r using them to reduce the conflicts b/w users, then views are always conflict less, each user have its own snapshot of data for each view. - if u want to speed up ur report by using temp views then it will not improve ur report's speed. - You have to create a temp table with all the join conditions and where clause, using variables in where clause to reduce the dataset for each report which is based on a view with large dataset. that way u will see ur reports work much faster. - I don't have the idea how to create a temp view using QB but it will always be beneficial to create a temp table or temp view using a create view / table command becoz this way u have more control over ur table/ view and code also. Off course, u can create temp tables /views on the fly using variables with the create table / view command before running a report. u can do it in a script / R:base command file. - it is recommended to reduce lookup variables in the reports. Regards Rehan Hamid Wyne On Thursday, June 26, 2014 9:05 AM, tfred <[email protected]> wrote: We have had a problem of multiple machines dropping R:Base in multi-user while creating complicated reports and we are working our way through it. In RBase-l archives, we keep finding suggestions on isolating users. I just changed all our PROJECT commands to TEMP TABLES WHERE LIMIT = 0. Previously used SomeID = 0 which works, but I see how LIMIT can avoid some conflicts which could lead to our problem. Now all REPORTS are being converted to TEMP VIEWS. The smaller reports work great. I am working toward a very large report (15-20 pages) which summarizes a lot of data. It is based on 12 table/views, 7 of which are multi-table views. Several questions: 1. Is it better to create new TEMP VIEW for each individual data table being used (major rewrite needed) or TEMP VIEWS of the existing VIEWS (minimal rewriting)? I assume regular VIEWS are functionally like TABLES. 2. Is there some way to create the TEMP VIEWS with the Query Builder then reload them on the fly using variables or just use QB to build the SQL code that creates the TEMP VIEWS before running the report? I have worked on this before and sometimes the light bulb of understanding just takes a while to come on. Tom Frederick Jacksonville, IL
