Daniel,

VBScript.RegExp is part of windows IE - I trust it to remain in the long run and I've been using it since XP

In case you're not very familiar with regex - download the pdf here http://www.atoutfox.com/articles.asp?ACTION=FCONSULTER&ID=0000000748



>Hi Gregory,
>
>Thanks for jumping in:)
>
>A couple of questions, should you have already used them - and, even better, deployed them on a relatively wide scale.
>
>I have not tested regex(es) from VFP. Sure that could help. But I try to avoid bringing extra system-levels depencies as much as I can. I understand that CreateObject("VBScript.RegExp") would bring access the MS-W scripting engine. Which mean a dependency on an MS-W* functionality.
>
>Does that mean risk on the long run or can I really trust the service on the long run? I have some issues with the idea of using them as an external resources except if the integration can be fully and neatly performed i.e.the regex engine is robustly embedded into the application.
>
>I currently embed all resources that are used into the package. On top of vfp runtime dlls, I a bunch of system levels dlls just to make sure that dependencies may not break the stuff in the longer run (xml parser, gdiplus and others...). Can I do the same with MS-regex service? Including on legacy XP install?
>
>Daniel