Warren, Wouldn't the only answer to this be "It depends"? How many tables? Lots? okay I don't know of an upper limit on table fields but I'm sure there would be a point of diminishing returns. How many columns? A few times Lots of tables? Still okay . Now, How many rows? A few for each table? Again, it's probably okay. I guess I am lost on the "filter operations part". Table fields will always be connected and activated by some client side event. "Click to refresh" or some PERFORM-ACTION-TABLE-xxxxxxx AL or Run Process. Keep it to a manageable number, don't refresh them all at once and you should only hobble your system, not cripple it. Seriously, it really all depends on the scope of the underlying forms. The more complex the retrieval method the more overhead. Does the EXTERNAL keyword cause an extra layer of traffic or does it help short circuit the query? What about Loading a temp table (form) and pulling that into one table with mixed columns. Like the Helpdesk Control panel ( Sorry, I don't know the real name of the conglomerate table for Incidents, Problems Service requests et al.) mid week musings John J. Reiser Software Development Analyst Remedy Administrator/Developer Lockheed Martin - MS2 The star that burns twice as bright burns half as long. Pay close attention and be illuminated by its brilliance. - paraphrased by me
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Warren Baltimore Sent: Wednesday, March 28, 2007 5:08 PM To: [email protected] Subject: Table Fields ** ARS 7.0.1 SQL 2000 OK my friends, just for "kicks", here's a fun little question..... What are the limitations (both real and theroetical) to putting LOTS and LOTS of Tables on a form. What would be the limitation (performance certainly being the big one). Is there a real limit? If the tables are only accessed via filter operations, would that make it better? I can't give any concrete information regarding the tables other than they would probably be accessing seperate tables (for the most part) and would probably only have a few fields in them. -- Warren R. Baltimore II Remedy Developer UW Medicine IT Services School of Medicine University of Washington Box 358220 1325 Fourth Ave, Suite 2000 Seattle, WA 98101 The opinions expressed in this e-mail are in no way those of the University of Washington, or the State of Washington. They are my own. __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
