Apr 12, 2004 #1 stewm MIS Oct 10, 2003 171 CA Can anyone explain the pros and cons of not allowing a single join in a catalog by letting the database do any joins that are required. Are joins a good thing to avoid in the catalog? Mark Stewart Consultants Club Corp.
Can anyone explain the pros and cons of not allowing a single join in a catalog by letting the database do any joins that are required. Are joins a good thing to avoid in the catalog? Mark Stewart Consultants Club Corp.
Apr 13, 2004 #2 DoubleD Technical User Apr 2, 2001 766 US Setting Joins in the catalog only tells your database how to join the data, it doesn't mean Impromptu will do any of the work. If your database is set up properly, the general rule is to have the database do as much processing as possible. Pain is stress leaving the body DoubleD Upvote 0 Downvote
Setting Joins in the catalog only tells your database how to join the data, it doesn't mean Impromptu will do any of the work. If your database is set up properly, the general rule is to have the database do as much processing as possible. Pain is stress leaving the body DoubleD