This problem has been plaguing me for years.   The DXL code is menu driven to select up 18 quality checks on a formal module.  The first time it runs I get "Exception Access Violation " error on a command to set (f).  However every subsequent time I run it, the errors goes away and program runs perfectly.   The error never shows up again unless I shut down DOORS and restart. 

The code is on a separate network so I can paste it here and it is over 1400 lines  so I cant type it in.

Any suggestions?

If you get 'Exception Access Violation' then I think that usually means that DOORS has crashed so it is strange that you are able to continue the session and run the code a subsequent time.

There are few known defects related to DXL and filter:

APAR PM97551 diagnostic log when reapplying filter on enumeration using DXL

APAR PI76082 - Applying a filter on a specific layout DXL column produces a diagnostic log

I'd suggest you to try to reproduce that issue with a smaller DXL script so then you can open a support case and get help from IBM support.

Regards