Hi Emmitt and all, It would appear that most of my problems with R:Charts were self inflicted based on an incorrect perception as to how to best develop and use charts. Your comments have been immensely helpful in "setting me straight".
I hope the comments have helped others who have dipped their toes in the charting waters as much as they have helped me. :-) Best regards, Michael Michael Moser EXAQ Micro Services www.exaq.com Phone: 916-966-8313 Fax: 916-966-8313 >> > >> >It seems that 3 reasonable enhancements to the basick R:Charts would be: >> > >> >1. ability to use R:Charts while connected with R:Base (Sami - based on >> >your comments - I am guessing that there is some way to access charts >> from >> >R:Base once they have been created, I just have not figured that part out >> yet.) >> If you have purchased a multi-user version of R:Charts this is no >> problem. I can work in the R:Charts designer while the db is open with >> MULTI ON and STATICDB ON. >> >2. The ability to pass "Where" conditions as part of the chart. >> For my part this is a non-starter. If you use the technique that most of >> us do - create a temp table (or view) on which the chart is based, write >> some R:Base code to load the table, then invoke the rbl, you will have no >> need whatever to pass a where clause to R:Charts. Simply limit the data >> in >> the table or view as appropriate. This requires that while developing the >> >> chart format itself the table is "permanent" in the database. Once the >> chart is developed, drop the table/view and make it temporary as noted >> above. >> >3. The ability to set users to deal with R:Base security implementations. >> Again, if you follow the strictures in 2. above, this is a non-starter. >> Emmitt Dove >> Manager, DairyPak Business Systems >> Blue Ridge Paper Products, Inc. >> 40 Lindeman Drive >> Trumbull, CT 06611 >> (203) 673-2231 >> [EMAIL PROTECTED] >> [EMAIL PROTECTED]
