bobsmallwood,
Yes, open the form in design mode, apply the filter, and then save the form. Having said that, I discourage this for three reasons:
1. In some versions of Paradox, closing a form containing a filter leads to a GPV (or whatever).
2. It's very easy to forget that a filter is applied. Thus, you may end up adding duplicate records or otherwise wondering where the rest of your data is.
3. Filters are applied before the form is displayed. If you're working with a network connect and have a lot of records in your table, your users may think Paradox has hung because there's no visual feedback while the filter is processing. This leads to table corruptions and other bad, icky things.
It would be best to use ObjectPAL to set the filter after the form as opened. For faster results, use a range instead.
Hope this helps...
-- Lance