logo

New Response

« Return to the blog entry

You are replying to:

    • avatar
    • Niel
    • Posted on Sun 7 Aug 2005 10:15

    Greg-

    Great idea, I had tried this once before but couldn't get it to work, seeing your comment lead me to do try it again. It appears (6.5 client/server) that it only works if you use the generic name as the first alias. This makes it hard to see your real alias name in designer because it only shows the first alias name in the view listing.

    For those questiong why not just use $$ViewTemplateDefault consider this common scenario:

    I have a 100% web based applications with ~10 views for the customer side of the app, these are (now) displayed using $$ViewTemplate for cust, There is also an admin side that is (now) displayed with $$ViewTemplate for admin, $$ViewTemplateDefault is the same form as $$ReturnGeneralError to help secure lookup views from being exposed.

    All of my views have three names 1)User Friendly 2)View type (cust,admin,sys) 3)Alias for script access.

    The only minor drawback is that if you want to NOT use the $$ViewTemplate for cust you have to remove the cust alias. I tried using $$ViewTemplate for User Friendly and $$ViewTemplate for ScriptName to override the $$ViewTemplate for cust, neither worked.

Your Comments

Name:
E-mail:
(optional)
Website:
(optional)
Comment: