I created the "Bordermanager Filters.mdb" database to help me in managing the BorderManager TCP/IP Filters I created. 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). The database also contains a table of the Built-in Protocols and those you created (as shown in the "Protocol Parameters" table). The database was created to run in an Access 2000 application and uses Excel as well.
April 4, 2005 - Made changes to the database to fix import problems. Also, changed the text file cleanup process to use Excel only. If you had used the previous version, you can delete the Macros in Word. Note: You now only have to copy the Builtin.CFG and Filters.CFG file to the default locations "C:\BorderManager Filters". If you want to change this location, you will have to edit the Macros in the Excel file. I added a new check to verify whether there are duplicate protocols entered into "Protocol Parameters" table. The duplicate entry will have to be deleted first.
NOTE: 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.