Virtual links vs. real links

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Studying http://opensource.21st.de/tiki-index.php?page=Beyond+Advanced I'm curious why I would use virtual links as opposed to "real" links? In other words, instead of doing a virtual link, why wouldn't I just add it to my links.ini file and let FB figure out that it's a link? It's not like it'd make much sense to have a link to another table, but not have that tables PK in the current table anyway. Or would it? Also, I can't see much use for making a text field turn into a dynamic link in case where "links" is typed in, but I could easily see a use for the converse: switching from a link to a regular text field if the value is "Other"... and in fact I will likely end up doing that if there isn't some example of it already out there that I can cut and paste. Or, it seems like virtual fields would be useful for a combo field: a combination select box and "other" box. The insert() and update() fields would then check to see if the select box's value is "Other..." and insert the value of the virtual "other" field in that case, and return its last_insert_id and put that into the selectbox's field and then insert/update that... ugh. Again, I'm surprised if there isn't example code of that online already, but if not I don't think it'll be to difficult to cook up. - -ken - -- - --------------- The world's most affordable web hosting. http://www.nearlyfreespeech.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFB1fIBe8HF+6xeOIcRAsNgAJ48ZhlDE9485/497tfwmU6nRhl7hgCg58KV 33tvOFVkpj60eg9+jRV3ySg= =66rX -----END PGP SIGNATURE-----