Nope, sorry that didn't do it. All it did was dump a pile of info into the page that I don't want shown.
It should be simple, in a template that displays the basic info for a person, name, city, photo, comment etc. I want to bring in other details from other tables such as this persons schedule list or sponsors (so a keyword search is required). This other info is contained in different tables because the main table would be too large with the info included and it is easier to control that way. Unfortunetly some of these other tables cannot be related because I need to use a different Primary Key in them (unless I missed something else).
In related tables data from other tables aparently can be brought in and displayed with <%Dbsql::Relation::HTML::generate_description('Author','AuthID','AuthName')%> Is there a better way to do this, hopefully so it will bring in all the data taht applies to this person with a keyword search added ?
How would it be done for un-related tables?
It should be simple, in a template that displays the basic info for a person, name, city, photo, comment etc. I want to bring in other details from other tables such as this persons schedule list or sponsors (so a keyword search is required). This other info is contained in different tables because the main table would be too large with the info included and it is easier to control that way. Unfortunetly some of these other tables cannot be related because I need to use a different Primary Key in them (unless I missed something else).
In related tables data from other tables aparently can be brought in and displayed with <%Dbsql::Relation::HTML::generate_description('Author','AuthID','AuthName')%> Is there a better way to do this, hopefully so it will bring in all the data taht applies to this person with a keyword search added ?
How would it be done for un-related tables?