-
FlexPro
- At a Glance
- Features & Options
- Applications
- All Advantages
- What’s New in FlexPro 2021
- Try FlexPro For Free
- FlexPro View OEM Freeware
- Buying Guide
- Login
- Language
- +49 6894 929600
- infoweisang.com
- Google Maps
- Products
- News
- Support
- Company
- Contact
- Login
- Language
- +49 6894 929600
- infoweisang.com
- Google Maps
deploy import filter
Home > Community > Automation and VBA > deploy import filter
- This topic has 3 replies, 2 voices, and was last updated 16 years, 8 months ago by sepp herberger.
-
AuthorPosts
-
February 26, 2008 at 7:34 pm #12394sepp herbergerMember
Dear,
I developed one import filter for customer. but the deployment for the filter seemed difficult for customer user, he should import my vba source code into his flexpro macro environment and run filter_register and filter_deregister etc,.
Is there any easy way to deployment customized import filter?Thanks in advance.
TanyaFebruary 26, 2008 at 7:34 pm #8077sepp herbergerMemberDear,
I developed one import filter for customer. but the deployment for the filter seemed difficult for customer user, he should import my vba source code into his flexpro macro environment and run filter_register and filter_deregister etc,.
Is there any easy way to deployment customized import filter?Thanks in advance.
TanyaFebruary 26, 2008 at 8:13 pm #8611Bernhard KantzParticipantTo 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 AutoExec or AutoOpen (see the article on Auto macros in the online help and the import filter example). De-registration should occur in AutoExit or AutoClose.
All this can also be automated by using the object model of the Visual Basic Environment. Please take a look at the VBE property of Application for the entry point to this object model. You will need to add a reference to Microsoft Visual Basic for Applications Extensibility 5.3 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.comFebruary 28, 2008 at 12:43 pm #8612sepp herbergerMemberThanks very much.
-
AuthorPosts
- You must be logged in to reply to this topic.