Re: DB_DataObject 2 joins to same table

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Nov 29, 2004 at 03:10:42PM -0800, Justin Patrin wrote: > > > > Although I find *visually* presenting this kind of relationship really, really hard in > > FormBuilder. My application is structured like this, and I've been banging my head against the > > wall trying to find a clean way to design forms that deal with this kind of schema. > > > > It's called a crossLink. ;-) > � > 8rk�yWj
g�!�http://opensource.21st.de/tiki-index.php?page=Formbuilder+configuration+options#id598583ϱ�usbH��? > > My understanding of crosslinks and triplelinks, is that they generate a bunch of checkboxes. That's not what I'm talking about. I'm talking about how one enters and links back and forth to editing the crosslinked records. As a bonus, I need to show all the data for those sub-records in tabular form as a sub-table-- not just $fb_linkDisplayFields. Simple example: let's say, using the above schema, that I want to display all the data for a user, including all his or her cars. *Only* his or her cars. Likewise, I want to be able to add a new user, then add the cars for that user. Or, when editing that user's data, be able to add a new car to their record or delete one. Sure, I could use crosslinks to show an array of *every* car in the database, regardless whether it has anything to do with this user, and check off which are his or hers. But that's impractical in a database of hundreds of records, and it isn't what I'm trying to do anyway. I'm not sure I'm explaining myself very well, but suffice to say I'm pretty confident that crosslinks are going to do it. - -ken - -- - --------------- The world's most affordable web hosting. http://www.nearlyfreespeech.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBq8Qte8HF+6xeOIcRAvVRAKCRzAGA6zLr96XTnZhTNRC1VJoVMACgv4Zk L9Hp6o6LYowS3bEyq6fatJI= =+kx1 -----END PGP SIGNATURE-----