Hi Craig,
Yes, I'm a bit like you too. Good with the server backend - things Linux, mysql & php, but not so much on the browser side - JavaScript or css, etc.
I've also found the learning process to be steep, mainly because the nuBuilderPro documentation seems to be minimal, and a combination of old and new versions.
Anyway, I find testing sql queries with the phpMyAdmin tool to be invaluable when you're learning and developing.
In your case, for this issue, I suspect what you're trying to do is have the 'Real Name' of a person show in the browse list, rather than the ugly and pointless person index.
I've done this already, so I can tell you what has worked for me. I'll explain it in text, rather than screen shots or videos, so let's see if this makes sense to you ...
In the form general tab, you should see an SQL query, on RHS box. Usually, something simple is the default. "SELECT * FROM projects"
You might want to have the table ordered by one column, so add something like this "SELECT * FROM projects ORDER By project_id_txt" and your browse table will now be ordered by projects_id_txt content.
Now, you want to get the 'Real Name' data from another table (lets call it people), that has nothing to do with the original table (projects in my example)
So you use the magical powers of SQL to JOIN the 2 tables together, linking them by the 2 fields which have the common data between them.
In my example above, add "INNER JOIN people ON technical_contact = people_id".
The final query looking like this.
"SELECT * FROM projects INNER JOIN people ON technical_contact = people_id ORDER By project_id_txt"
In this query, technical_contact is a field of projects table, and people_id is a field of people table.
If you test this in phpMyAdmin, you will see that the result is the combination of both tables, with all fields being available to use now.
Then, there are 2 more things to do.
1. On the 'browse' tab, you need to add a column, referencing the new 'Real Name' field from the people table.
2. You need to make sure there is a matching 'object' in the objects list, which defines the field as text, with a width etc.
Took me a while to work out the need for the 'objects', so look at other objects too, and make sure you have one for your new browse field.
The other 'trick' I've figured out (or seen?) is to 'hide' a column you don't want to see in browse table, by setting it's width to 0 (zero). You can also delete it from browse objects, but depending on your sql query, this sometimes doesn't work.
Hope that helps!
Mark
saultpastor wrote:Thanks Mark,
I have gone back over the videos. it a steep learning curve for me for some reason. I have used linux on the desktop for years, even owned a web design company, in the early days before php, css, etc. not a lot of experience with php, javascript, or MySQL up to this point though.
I've been able to set it up to use lookup to select a record from another table and post it to the new table. But it only posts the primary key, I can't seem to get it to post from the name column that corresponds to that primary key.
