I created the "BorderManager Filters" database to help me in managing the BorderManager TCP/IP Filters I created. This database was created using Access 2003 and Excel 2003, but should work with Access 2000. The reports I created gives you a printout of these filters, compares the difference between the filters you think you have (as shown in the "Original Filters" table) and the actual filters in FILTERS.CFG file (as shown in the "Current BM Filters" table). T he database also contains a table of the Built-in Protocols and those you created (as shown in the "Protocol Parameters" table).
If you didn't create a new protocol
when you developed your BM filters you need to remark out the following in the Access Database Module1 CleanupFiltcfgFile() function:
This is done by simply adding a single quote mark in front of the statement. The statement calls the "Sub Protocols_Filters()" macro in the "Protocols-Cleanup.xls" excel file. This process assumes that you have created your own protocols. When you finally do, just un-remark the statement.
You will also need to remark out the following in the "ImportData()" Function:
DoCmd.TransferText acImportDelim, "Protocols Import Specification", _ "Protocol Parameters", strPath & "Protocols.txt"
This is done by simply adding a single quote mark in front of the statement. The statement imports the "Protocols.txt" file that the previous excel function would have created. This process assumes that you have created your own protocols. When you finally do, just un-remark the statement.
Changes for 04/21/2008 Version 2.8:
Added the ability to import single or multiple server filter in one step.
Changes for 07/25/2007 Version 2.4:
Added the ability to "Compact" the back-end database tables and the front-end database. Also, fixed the "Protocols-Cleanup.xls" excel file code to enable the import of filters.cfg file with no comments in the filters comments field.
Changes for 05/01/2007 Version 2.3:
Added the ability to import filters for more than one server. Reports filtered based on the selected server.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.