Our app is Runtime, so I haven't had any problems. Except... In Query/Edit they can "save" their query as a table, which has caused a couple of problems over the years.
Thanks, Dennis ***** At 12:52 PM 7/22/2003 -0400, you wrote: >Dennis, > >My admonition pertains mainly to an application that has been deployed in a >multi-user environment. Clearly, in development work this does not hold. > >Various developers take differing views on how much access users should >have to the tools in R:Base. Some let users have full access to the report >writer, forms designer, RBDE, etc. We, on the other hand, never want a >user to reach an R> or have access to the development tools. STATICDB ON >is a way of preventing even inadvertent changes to the schema. With over >350 forms, over 350 reports, and in excess of 550 command files in an >application running at five locations driving the business front-end and >manufacturing back-end, we simply cannot afford any uncontrolled changes to >the database, its structure, tables, indexes, etc. > >Ours is clearly the conservative approach. > >>Emmitt, >>(Just getting back to this thread) >> >>You mentioned: >>"Just one word of advice - run with STATICDB ON." >> >>With Staticdb ON, I can't go into Table Definitions, but I can add a column >>to a table: Alt Tab XXX add Column ... >> >>What is the reasoning/pitfalls behind Staticdb ON/OFF >> >>TIA, >> >>Dennis >>***** >> >> >>At 03:11 PM 7/18/2003 -0400, you wrote: >> >Dennis, >> > >> >The beauty of a temporary table or view is that it is specific to the >> >user. So five different users can all create the same temporary table with >> >the same name and not interfere with the others. Therefore, the drop >> >before create should only affect the user running the program. I always >> >drop after I am finished with the table or view. >> > >> >Just one word of advice - run with STATICDB ON. >> > >> > >> >>RBase 6.5++ >> >> >> >>In the process of converting lots of tables/views to Create Temp >>tables/views. >> >>But, since this is a multi user app, only time I disconnect (and they are >> >>deleted) is when they load a program update or Reload their data base. >> >> >> >>So, I have Drop view/table before (and after?) each code segment that >> >>creates them. If a second user comes along and tries to run the same piece >> >>of code before the first users exits... it works just fine. I didn't >> >>realize the temp tables/views are saved with each user and you don't have >> >>to worry about duplicate table/view names. >> >> >> >>But, what about deleting them before/after the code is run? >> >> >> >>TIA, >> >> >> >>Dennis >> >>***** >> >>Dennis Fleming >> >>IISCO >> >>http://www.TheBestCMMS.com >> >>Phone: 570 775-7593 >> >>Fax: 570 775-9797 >> > >> >Emmitt Dove >> >Manager, DairyPak Business Systems >> >Blue Ridge Paper Products, Inc. >> >40 Lindeman Drive >> >Trumbull, CT 06611 >> >(203) 673-2231 >> >[EMAIL PROTECTED] >> >[EMAIL PROTECTED] >> > >> > >> > >>Dennis Fleming >>IISCO >>http://www.TheBestCMMS.com >>Phone: 570 775-7593 >>Fax: 570 775-9797 > >Emmitt Dove >Manager, DairyPak Business Systems >Blue Ridge Paper Products, Inc. >40 Lindeman Drive >Trumbull, CT 06611 >(203) 673-2231 >[EMAIL PROTECTED] >[EMAIL PROTECTED] > > > Dennis Fleming IISCO http://www.TheBestCMMS.com Phone: 570 775-7593 Fax: 570 775-9797
