Yes, they are not the best practice any more. Best practice is to accumulate records in a back-end form and use a PK/FK relationship to tie them to a master record (i.e. Work Logs to an Incident. Reporting can be challenging, but a join at the reporting level should make things easier.
Rick Cook On Mon, Sep 29, 2014 at 3:30 PM, Reiser, John J <[email protected]> wrote: > ** > Hello Listers, > I have quick question. > What is the general consensus on the use of Diary fields? > Are they going out of style? > I have tried a “work log” table type of design to replace the diary > function on a form. > This method works ok except when it comes time to run reports. > Do you dump the table field data to a large character field? > Or is there a slick way to incorporate the child records into the report > on the fly? > > Thank you, > --- > John J. Reiser > Remedy Developer/Administrator > Senior Software Development Analyst > 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 > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
