What is the best way to create a simple rule based on a NULL recordset value?

I've always had trouble with this even when hand coding. I usually end up either putting in a default value in the database for comparison purposes, or create a recordset and perform the action depending on whether or not the recordset is empty. But I'd really like to do this, if possible the way the database is set up, and use the Rules manager.

I simply want to show the image is the recordset value for a particular field is not Null, and not show the image if the value is NULL.

When creating the Rule, I can either use Allow or Restrict. Which would e the best one and what would the comparison be to the recordset value?

I tried using Restrict, selected the recordset field, the Equals sign, and left the comparing field empty. This is what I do for Page access to check if the Sessions variable for a Logon ID is set and it works.

This time however, after the Rule is created, I select the Rule, and the image doesn't display although it should. I then tried selecting the "Not" version of the rule, and get an error

Parse error: syntax error, unexpected ';', expecting T_PAAMAYIM_NEKUDOTAYIM in /home/content/65/9860265/html/Profile_Preview.php on line 126

So, is it just not a good idea to rely on null values for these things? Or is there a better way to create the rule? I do understand the difference between NULL and something that just doesn't contain any data.

I've found the source of the error, but still can't get the rule right.

When I apply the behavior to the page, I notice in the code it's placing the HTM: markup for quotes around the rule name in the IF statement

<?php if(WA_Auth_RulePasses(&quot;MyRule&quot;))...

This also causes and error when I go to open the show Region dialog from the Server Behaviors panel - it says that the rule is no longer defined. So I change the markup to just regular quote symbols and all those errors go away. This does not happen when using Page Access. I'm using DWCS 4 on windows, and Sec Assist 1.1.9.

Is this a bug or a setting or just some random outcome because of a convergence of different things? Either way, it's not a big deal to work around, I'd still like to be ale to get my rule properly defined.

Security Assist Access Rules cant be used for this.

you need to hand code the if statement for checking for null values:

<?php if ("".$row_recordsetName['ColumnName']  ."" != NULL) { ?>

it's not null

<?php } else { ?>

It's Null

<?php { ?>

Thank you Jason for once and again going above and beyond and providing the cole. I do understand what you mean, and I still don't like NULLs in any case, but I thought I would give it a go. Plus, I like using my tools whenever I can!

What about the error issue where the Rule name is enclosed in the &quot; markup and not the actual quote symbol?

And lastly, I did try using a default database value as a comparison for the rule in various combinations without success, but I will post a new thread on this if I need to.

Thanks again!

  What about the error issue where the Rule name is enclosed in the &quot; markup and not the actual quote symbol?  

I've not been able to reproduce this, I would say it's a random fluke, if it happens again, let us know, and we'll start an incident to investigate.

Yeah, i would say random fluke too. i'll keep an eye on it, but the work around is simple enough and easier than to try an troubleshoot whatever combinations of code there is on the page that's probably contributing to it.

Overall, this part of Security Assist is one of my favorite tools to use - it really adds an element of professionalism to a site especially with the various options there are, such as using groups and being able to apply rules to multiple pages for larger sites.