Null Error on Report Opening

[Lowell]

I have a report that opens with data drawn through a query, really simple, straight from a table. In the query one of the fields is this formula:



MemberSymbol: IIf([MemberStatus]=1,'',IIf([MemberStatus]=2,"*",IIf([MemberStatus]=3," (ex)",0)))

Earlier today it was this:

MemberSymbol: IIf([MemberStatus]=1,Null,IIf([MemberStatus]=2,"*",IIf([MemberStatus]=3," (ex)",0)))

I was getting this message:

Invalid use of Null

So I changed it to the top formula, but I still get the same warning.

The query opens fine by itself and the WHERE statements generate correctly. It is only when I open the report that it throws the code. The macro that opens the report throws 'Error 2950'. I have the file location trusted. When I open the report straight from the list of reports on the left side it also throws the warning. So I know it's only when the report is opening.

I can't find any other Null argument anywhere in connection with the report.

Any thoughts on what to try?

I have attached the Front End in the zip.

[June7]

Which query and report? Would be nice to have data to work with. Make a copy of db and import tables or provide the backend as well.

[GinaWhipp]

Can you post the entire SQL of the recordsource? There may be a clue there.

[Lowell]

I'm really sorry for wasting your time. I was a little leary of posting personal data, so i made some fake data so i could post the backend on this forum.

Well, i tried the report before i posted it and it worked excellent, so then i was really confused and assumed it was the data.

I copied the backend and frontend and started deleting data. Thankfully i was lucky enough to start at the right end. I found the record that was causing the issue. The table fields were all set to not required except the Primary Key, and yet when I added in the basic data, the report populated correctly. So we'll see if my client's program will fix that easily as well, fingers crossed...

I will mark this solved, even though I don't really understand how the lack of data caused the issue.