G'Day Dennis,

Feel free to say that the following is not something you would have me do. There may be alternatives already in Logic, that I am not aware of. I am aware of the "pattern match" filter, but it would seem to be limited to "*" and "?". My addition of the FLL may interfere with some plans you have for the future.

I have found a Foxpro FLL library to perform a "regular expression" on a piece of text. See Foxpro FLL for Regular Expression matching - Part 1 Part 2 Part 3

It gives one the ability to filter like this ....

REGEXP(ALLTRIM(CALL),"VK[345][A-Z]{2}")

... and in my log it finds all VK3, VK4, and VK5 two letter call signs - all 123 of them. The regular expression syntax seems to be based on that for PERL.

Currently I load this FLL by running a "Miscellaneous utilitiy" than has one line of code ...

SET LIBRARY TO "regexp.fll" ADDITIVE

... the FLL being in the main Logic folder.

I have successfully run the "test" programs in the documents above. Logic carried on, no problems. I have been using the FLL call in my filtering, and again, so far, I have seen no problems.

I can see what I can do, but I want to clear it with you before I commit any more time to it. It can see it becoming pervasive in my system.

Also, if you see no real problems, what mechanism is available to me to add the "SET LIBARY ADDITIVE" to the startup of Logic - rather than manually run the Miscellaneous utility from the menu each and every time I load Logic.

Peter VK4IU

... thanks for that Dennis.

I use VBSCRIPT.REGEXP in VBA code in Microsoft Outlook. I parse DX Bulletins as they arrive as emails, creating personal calendars and "alarms" for myself, and saving the emails in a form suitable for VE3NEAs Bulletin Reader.

Peter VK4IU