Dan, The only difference is that one equates to the 'magic number' generated by Witango - and you must manually include the "_userReference=" Search Argument - while the other automatically includes this Search Argument.
Put another way, you either use: <a href="<@CGI><@APPFILE>?_userReference=<@USERREFERENCE>"></a> ...or... <a href="<@CGI><@APPFILE>?<@USERREFERENCEARGUMENT>"></a> ...the result is the same. To prove that, create a TAF/TML as below: <html> <head><title>Testing</title></head> <body> <@LITERAL '<@USERREFERENCE>'> = "<@USERREFERENCE>" <br><br> <@LITERAL '<@USERREFERENCEARGUMENT>'> = "<@USERREFERENCEARGUMENT>" </body> </html> So, you should be able to use either - and it shouldn't make any difference which you choose. You can, for example, use both in a project, provided you remember to include the Search Argument where relevant. My guess as to why both exist is simply that the <@...ARGUMENT> was added at a later date to reduce code clutter - if you have to manually type the Search Argument on every hyperlink, and it has to be the same name every time, why bother to re-type it?! Put another way, I'd suggest that the <@...ARGUMENT> one is best, but the pure version remains for backward compatibility. Jon -----Original Message----- From: Dan Stein [mailto:[EMAIL PROTECTED]] Sent: 10 May 2002 12:03 To: Multiple recipients of list witango-talk Subject: Witango-Talk: Silly Userreferance argument Seems I have sometimes used Userreference and sometimes userreferance argument in my growing application. I would think it is important to be consistent and use one or the other but not both. I had at least one incident where clicking on a links where they were different ended up bring up someone else's information. So which is best to use or are their times when one is needed instead of the other? Should I change them all to one or the other? Why do we have both? Dan -- Dan Stein Digital Software Solutions 799 Evergreen Circle Telford PA 18969 215-799-0192 610-256-2843 Fax 413-410-9682 FMP,Tango, EDI,SQL 7 [EMAIL PROTECTED] www.dss-db.com ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
