Warren, I think you hit it with performance. There are some many if's that can come in to play. Number of records returned in each table, the tables referencing join forms, indexes on the forms, etc.
I've created a display only form that has 4 table fields. Workflow runs a Active Link Guide looping over the primary table of between 2 to 3 thousand records. The guide drives table refreshes on the other 3 tables. I couldn't figure out how to refresh the tables using filters so I used active links. Others probably have more complicated processes with more tables. Dave -------------------------- [EMAIL PROTECTED] (Wireless) ----- Original Message ----- From: Action Request System discussion list(ARSList) <[email protected]> To: [email protected] <[email protected]> Sent: Wed Mar 28 17:07:30 2007 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___
