Dear David and Adam, I have run into a problem with having two references to the same table in different fields within the same record. In this case, I have two different references to the contacts table (AppointmentSetFor and AppointmentSetWith).
As I am sure you are aware, it is only the view action that are effected and therefore I guess the Edit action as well. The insert works OK. As I work through this application, I will have several such situations. I understand this is a problem for PLUM. I am guessing it is a problem with the way the custom tags stack and not the IDE. If it is the ide then all I have to do is hand code the effected templates using PLUM custom tags, that would be VERY SWEET. But it does not seem likely. I am also wondering if the problem with table aliases is in the SELECT part of the SQL or the WHERE clause. For all the situations I can foresee, if I can use the WHERE clause to filter the results of the SELECT statement then I can use session variables to complete the information needed by the user. i.e.. APPOINTMENTS NEXT WEEK FOR <cfoutput>#session.currentuser#</cfoutput>. This would result it only having to have one reference to the table instead of two. How do you guys deal with this? I want to maintain the same format throughout the app. I want all the pages to look just like they were PLUM pages. Thanks a whole bunch, Mark Fuqua ********************************************************************** You can subscribe to and unsubscribe from lists, and you can change your subscriptions between normal and digest modes here: http://www.productivityenhancement.com/support/DiscussionListsForm.cfm **********************************************************************
