When I attempted a NOFILTER query with FPD2.5, the NOFILTER did not cause an error. However, it did not cause a separate table to be created. The question is, what effect are you trying to cause?

As NOFILTER was explained to me (thank you Jim Booth) it forces VFP to create a separate table when a filtered query is unacceptable for various other code reasons. The filtered query is the faster option though.