building a view across multiple node references
I'm working on a site that uses Ubercart and contains a content type called "product". Each "product" node has a node reference field to nodes of type 'foo'. Each 'foo' node has a node reference field to nodes of type 'bar'.
If the user clicks on the link for a product, I want to display all the fields for each 'bar' node that is referenced by each 'foo' node for that product. So far, I haven't figured out how to do that.
Is it possible? If so, how?

I believe you can do this
I believe you can do this using the NodeReferrer module. I just started playing with this last week.
http://drupal.org/project/nodereferrer
Mark W. Jarrell
Manager of Web Services
Jones Knowledge Integration Group, Inc.
http://fleetthought.com
http://www.jones.com
http://www.jonesdifference.com
http://www.jiu.edu
Twitter: attheshow
making progress...
Thanks, Mark, for the suggestion. I have seen nodereferrer, and other modules like it, but I'm trying to stay away from them if I can. I have made some progress since my last post, though:
Again, my example was as follows:
"Product" node contains node reference field to-> "foo" node, which contains node reference field to -> "bar" node, which contains a bunch of fields, but no node reference fields.
Using my example, I figured out how to create a view that takes one argument - the node id for a product - and lists the name of the product and then some fields from a node of type 'bar'. I used a couple relationships to pull it off.
Now I want to go the other direction: I want to display the node title for "bar" node, and then list product title that is associated with it. The relationships that I set up don't work, of course, since the node reference fields don't exist the other direction.
I am aware of the corresponding node reference module, but, again, I'm trying to avoid going down that route. I'd like to avoid the need to create a node reference in every node that we create. However, if there are any experienced drupalers out there who need to inform me that I'm crazy for avoiding the corresponding node reference module, please do let me know. I'm very much interested in learning best practices for cases like this.