Thank you Joe...i appreciate your help. Have a great holidays ________________________________
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Friday, December 21, 2007 2:25 PM To: arslist@ARSLIST.ORG Subject: Re: QUESTION: Table ** What I do is something similar and had even recommended this on the list.. for exactly the same reason Michael pointed out.. So if I were to create a table field for a table called HPD:HelpDesk for eg on a column called Request ID, My table name for that table would be.. TBL_HPD_HD.. The Request ID appearing on that table field would be called COL_HPD_HD_RequestID.. This way I have all tables listed together on the drop list of fields, and all columns belonging to that table listed together as well.. I also have field id conventions of my own that I use for these. I usually start table field ID's in the 9 million range.. so the first table field on a schema would have a table field ID of 910000100 second table will have 910000200 etc.. Columns from the first table would be starting with 910000101, 910000102 etc... Anyone who has worked with me from this list might have noticed that.. I have found a lot of advantages of using conventions like this.. Every data or display only fields that I usually create also have ID conventions like this.. a form that would have taken 20 minutes to build might take you an hour, but its worth both that time and efforts.. What I do at the beginning of every project is preselect either a 6 or 7 million range to use or (or 7 or 8 / 8 or 9 million). Usually I am more biased towards the 8 and 9 million.. I use the 8 million range for data fields, and subdivide the 8 million range for various kinds of data such as people data, application 1 data, application 2 data etc.. and use the 9 million range for table fields, buttons, trim fields etc.. where 91 would be prefixed for tables, 92 for buttons, 93 for boxes.. etc.. Cheers Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Dwayne Martin Sent: Thursday, December 20, 2007 12:22 PM To: arslist@ARSLIST.ORG Subject: Re: QUESTION: Table Michael, Good idea! Thanks, Dwayne ---- Original message ---- >Date: Thu, 20 Dec 2007 10:17:28 -0700 >From: "Durrant, Michael M. - ITSD" <[EMAIL PROTECTED]> >Subject: Re: QUESTION: Table >To: arslist@ARSLIST.ORG > >I'm a fan of using col_<tablename>_<columnname> - it makes for easy >sorting in lists and I can tell what it's for just by looking at the >name. > >-----Original Message----- >From: Action Request System discussion list(ARSList) >[mailto:[EMAIL PROTECTED] On Behalf Of Dwayne Martin >Sent: Thursday, December 20, 2007 9:31 AM >To: arslist@ARSLIST.ORG >Subject: Re: QUESTION: Table > >The column name for the Request ID will have a name like "Column3". In >order to make the workflow easier to understand it usually helps to >rename it to something like "Request ID col." > >Dwayne Martin >James Madison University > >---- Original message ---- >>Date: Thu, 20 Dec 2007 10:05:00 -0500 >>From: "Joe D'Souza" <[EMAIL PROTECTED]> >>Subject: Re: QUESTION: Table >>To: arslist@ARSLIST.ORG >> >> ** >> Rob, >> >> On the open window action of the dialog, pass the >> request ID from the table field into the dialog on >> the Open action of the dialog, and have an active >> link that executes on Window Open, and Runs If >> $OPERATION$ = "DIALOG" which sets all the fields in >> the dialog where 'Request ID' = $Request ID$ >> >> Joe D'Souza >> >> -----Original Message----- >> From: Action Request System discussion list(ARSList) >> [mailto:[EMAIL PROTECTED] Behalf Of Rob >> Cvetkovski >> Sent: Thursday, December 20, 2007 9:48 AM >> To: arslist@ARSLIST.ORG >> Subject: QUESTION: Table >> >> I have two forms, Form "A" with a few fields on it - >> 3 of the fields are Display Only. When the user >> enters the data into the 3 display only fields and >> hit a button that I created it pushes those 3 >> display only fields off to Form "B". This works >> perfect. >> >> Next I have a table on Form "A" that shows the >> records from Form "B", again this works perfect. >> >> What I am trying to do is when the user clicks on a >> row in the table and below the table they click on a >> button called "View" I want it to open a dialog >> window with the data of the record they selected. >> This is where I am having issues. >> >> Any help would be greatly appreciated. >> >> Thanks! >> >> Rob __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
