To add to my previous post, theoretically there should be no effect of the number of table fields you create on a form as a creation of a table field does not create a column in the T or H or B tables so even the underlying database restrictions of max number of columns a table can have won't come into play..
You however wouldn't want your forms to be so thickly populated with table fields that opening up your form on the client would create 10 terabytes of cache.. each table field will create a separate cache file on a client when a form is opened and you dont want loads of that stuff to happen.. it will severely hamper performance.. Joe ----- Original Message ---- From: Warren Baltimore <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, March 28, 2007 5:07:30 PM 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 ____________________________________________________________________________________ Don't get soaked. Take a quick peek at the forecast with the Yahoo! Search weather shortcut. http://tools.search.yahoo.com/shortcuts/#loc_weather _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
