Zxsiz,
Having the song name and album name fields match causes difficulties. You'll have better results if you take an alternate approach.
If those two fields match, you can use a rule like this in Set Rules for File Display:
[=IsEqual([Album],[Name],0)]=0
This rule will exclude all singles in your naming scheme. But it will also exclude non-singles that happen to match your naming scheme, namely the title tracks from albums. Like "Back in Black" on AC/DC's "Back in Black" Album. You could try and create other clever constructs to counteract this, like giving all singles a track number of 999 and excluding those. But that's a bit of a hassle.
The bigger problem is that singles are sometimes also released as part of an album. And if that album happens to be named after a track that was issued as a single, then you have a conflict: Two "albums" with the same name, one the single and one the actual album.
It would be better if you structured your album names for singles to include the word single, like this:
[Name]=Back in Black
[Album]=Back in Black (Single)
Then the two albums cannot be conflated, and it is easy to include or exclude from your view any album that contains the string (Single).
But if you don't like this idea, then what tij is doing, having a separate tag to identify the type of album, would be best.
There's another option of course: since singles are NOT albums, leave the album name blank. Then exclude such files from your album view and have a separate singles view. It an artist view, all the singles would be grouped together under an unassigned Album category, but that would be appropriate.
Good luck...