* Dr. Internet columnist Steve Blass has some MySQL database tricks * Help Desk columnist Ron Nutter discusses blocking ports on switches
* MySQL database tricks
By Steve Blass
Q: I have a MySQL database that needs to be converted or exported to a Microsoft Access database. I can connect to the MySQL database with Access using ODBC, but when I try to save or export the MySQL data, Access wants me to export each table individually. Is there a way to create a self-contained Access database file from the MySQL database without going through the export steps for each table in the database?
A: Instead of using the File/Open command in Access to connect to your MySQL database using ODBC and then exporting the individual tables, you can create a new blank Access database and then import the data from the MySQL database. Start with the File/New command in Access and create an empty database.
To read Steve’s response in its entirety, please click here.
* Blocking ports on switches
By Ron Nutter
Q: As our network continues to grow, we are trying have standards as to reserving certain port numbers for access points, certain ones for printers, etc. Another challenge is to prevent ports from being used without proper authorization. Just to make things really interesting, a previous administrator bought some Cisco switches used and never got any maintenance agreements on them, so I am not allowed to replace them until a significant of ports have gone bad. Is there a way that all of these ideas can be accommodated into one manageable solution?
A: One thing that I would do immediately is use the description command on each port to record what the port should be used for, what it is being used for – and when a port does go bad, that the port shouldn’t be used. When troubleshooting problem connections, being able to look in the switch and see where a connection is supposed to be can save a trip or two to the wiring closet.
To read Ron’s response in its entirety, please click here.
