To deploy a filter written in VBA you need to import the VBA source code in one of the template databases. The registration should than happen in either [i]AutoExec[/i] or [i]AutoOpen[/i] (see the article on Auto macros in the online help and the import filter example). De-registration should occur in [i]AutoExit[/i] or [i]AutoClose[/i].
All this can also be automated by using the object model of the Visual Basic Environment. Please take a look at the [b]VBE[/b] property of [b]Application[/b] for the entry point to this object model. You will need to add a reference to [b]Microsoft Visual Basic for Applications Extensibility 5.3[/b] to access the necessary type library.
Depending on what you can expect on the target system (module name or function name collisons, existing auto-macros etc.) this can be more or less work.
You can reduce deployment issues by implementing your import filter as a COM add-in. Thus you just need to deploy and register a DLL (and its dependencies). As FlexPro VBA is the same as in Microsoft Office the same literature applies for COM add-in development.
Support
support@weisang.com
