Who Gives a .... Anyway

I am busy migrating an Access system, and documenting, so I need a way to document the SQL Queries and Table details. After initially trying to get Access's documentation tool to give me what I needed, I started looking for alternatives. The below code is partly mine and based on the websites mentioned in the comments. Essentially it exports Query and Table information into 3 files in the tmp directory. I tried to do the SQL queries using CSV but even using "'" and """ did not work, so change it to TABS. This means that you can get most of the details for structures in a usable format (not like the Database Documenter which provides unusable details) so here is the code that I ended up with, thought I would share it: Public Sub GetQrysAndTbls() ' Using a few items found on the internet write query and table definitions ' to a text file including field detail for tables ' Original posts found at: ' http://www.techrepubli

Seem as there are a few forums out there that I had to scan through to find this I thought I would post this so that people can see how to get their VBA code from previous versions of Outlook across when they upgrade to Outlook2010. Macros and the Visual Basic Editor Now that you know something about how Office 2010 applications expose their object models, you are probably eager to try calling object methods, setting object properties, and responding to object events. To do so, you must write your code in a place and in a way that Office can understand; typically, by using the Visual Basic Editor. Although it is installed by default, many users do not know that it is even available until it is enabled on the ribbon. Opening the Developer Tab All Office 2010 applications use the ribbon. One tab on the ribbon is the  Developer  tab, where you access the Visual Basic Editor and other developer tools. Because Office 2010 does not display the  Developer  tab by default, you must enable it b