WshBuild(ing) Relationships

So far our meta-data file contains some very basic information about the databases type, name, properties, and linked tables The next item on my agenda was relationships. Now I was of two minds about this, and I still am. But here is how I went about implementing it anyway.

How to output properties and remove imaginary tables

After my work getting the WshBuild to output a Project.xml file, I needed to start populating the data in it. There were three things that I wanted to do from the very start in this file. First, I wanted information about the database itself: it’s name, type, etc. Second, I needed the project properties. Finally, I wanted to eliminate the linked tables from the source export.

WshBuild Progress – Sort of…

This past week I decided that I would indeed modify WshBuild to be able to regenerate a database from it’s exported source. Some of the things I came across were easier than anticipated, but others are turning out to be more difficult than I had initially imagined.

More work on WshBuild?

A while ago I posted about a little project I was working on for work called WshBuild. I’ve slowly been making tweaks to it as I need them at work. I have a couple of addins, one especially for MS Access.  This was the primary reason why I wrote it in the first place, to automate my build process for one of the databases I am in charge of.  I use the Windows Script Host because it makes COM automation a little easier for me. That allows me to control an instances of Access to perform things like mde/ade file generation, compacting databases, and other things.