Not recognize empty string in connected parameter?

(3 posts) (2 voices)

Tags:

No tags yet.

  1. spyhunter88, Member

    Hi,

    I use connected parameter with all Select List. But the second parameter does not run if has empty string value in previous parameter.
    Of course all list is String. See my code:
    /* First */ SELECT '' as ID, '(All)' as Company UNION SELECT Company, Company FROM Companies

    /* Second */ SELECT '' as ID, '(All)' as Store UNION SELECT Store, Store FROM Stores WHERE mydbr_param_prev1 = '' OR Company = mydbr_param_prev1
    But it seems the second Parameter does not work if I choose (All) in the first. I change the mydbr_param_prev1 is null instead of = '' but does not work too.

    Only I add an space into the First:

    SELECT ' ' as ID, '(All)' as Company ....

    AND the second compare to 1 space
    ... WHERE mydbr_param_prev1 = ' ' ...

    And it works now. But it's like a hard-code tricky because we'll easy to miss the one space.

    Please fix this so I can compare like mydbr_param_prev1 is null. And check it for higher level also, like the Third, Fourth ... parameter.

    Thanks

  2. myDBR Team, Key Master

    Simply use something else than an empty string. For example:

    SELECT 'All' as ID, '(All)' as Company
    UNION
    SELECT Company, Company FROM Companies

    --
    myDBR Team

  3. spyhunter88, Member

    I had used this solution for older version. But I love the empty string issue will be fix soon. :D

    Thanks,


Reply

You must log in to post.