Warren, At the risk of saying what you alreaady know knowing your experience with the system, I would definitely look for the following:
1) INDEXES on fields that are used in the qualification that qualify for indexes on tables that are called by these table fields. 2) Write the queries in the format where the 'Field Name' is to the left side of the $Field Name$ so the indexes defined on them would be used. 3) Chunk as many of these table fields as you can if you would not be using the $LASTCOUNT$ or similar keywords on ur workflow that counts entries on the table field in question. 4) Refresh only the necessary table fields on Window Open, Display, Undisplay, Window Loaded.. 5) And for your own good and the good of other developers who might have to take a look at your table sometime in the near future, have a naming conventions for the columns of the table and don't leave it as a default Column 1, Column 2.. etc.. 10 minutes after building the table when creating workflow for these tables you are harldy likely to know what Column 345 is if you do not have a good naming convention.. I thought the last one is the most useful tip for you in your situation.. The naming convention I follow is.. lets say I am having a table field on a Trouble Ticket Form.. I call this table field Tbl_TroubleTicketForm. The Request ID column for eg in that table field will be named Col_TTF_RequestID. TTF stands for TroubleTicketForm.. This way I have all the columns of a table field one after another in a sequence. I have similar conventions for Field ID's too that I use for stuff like table fields etc.. but you could come up with your own.. its not a hard and fast thing.. Just stuff that I came up with over the time I have worked with the AR System.. I have found these methods very useful.. Hope you find these tips of some use... Cheers Joe D'Souza Remedy Developer / Consultant, BearingPoint Inc., New Jersey. ----- 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 ____________________________________________________________________________________ Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games. http://videogames.yahoo.com/platform?platform=120121 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
