Windows Explorer style layout

[code_geek]

[color:blue]I need to figure out if its possible to create a Windows Explorer style layout, where I can create a list view of customers on the left-hand side, and write a script so that when a customer in that list is clicked, a list of jobs for the customer is displayed in the main body. Does anyone know if this is possible? I think I can figure out the scripting part, I just can't figure out the layout part...

Edited April 9, 2008 by Guest

[mr_vodka]

Sure you can have a portal on the left hand side that is a list of your customers. The script can set a global field with the customerID. A relationship from this global field to the customer info and hence related customer jobs can be displayed in another portal on the right.

[code_geek]

Ok, I've read up a little on portals and I think I get the general idea...

So I have two tables, the 1st has all the store name and address info - the 2nd has a field for the name only. I set a 1-to-1 relationship between the tables, and I don't think I need a unique ID yet because I only want to list the stores in the main table, using a script or other function to filter the results - its just for listing whats in the table. I'm having trouble understanding exactly what to do though. I can't even get a record to display in the portal...

Can someone give me an example that will at least help me get some data displayed in the portal? I figure if I can get that far, I'll understand what's going on. Can someone help shed a little light on how this works? Thanks everyone!

[comment]

See if this helps:

NavPortal.fp7.zip

[code_geek]

comment,

Sorry for my delayed response. I studied your example and I finally get it! Thank you! At first I had difficulty understanding how you used the ViewJobs and AllCustomers relationships as a filter. It also took me a while before I noticed the fields that you inserted into the portals and how the field in the AllCustomers portal was set up as a button, scripted to SetField 'gCustomerID' to 'AllCustomers::CustomerID', which basically tells the relationship object to change the filter to the CustomerID of the selected Customer. So complex, yet so simple!

This is exactly what I needed, comment. In fact, I see how you can add another column from the same table just by adding another field to the portal. How cool! So thanks again, I learned several things from your example!