Last year I started a new project to develop a COM Add-in for Excel, the DB Code Generator Wizard. For some reasons I decided to delete one vmWare setup where, of course, the code project was developed on. At that time I was not aware of that I had no backup for the utility. What is left of it is only some screenshots. Now I wonder if it of interest that it will be re-created or not.
The following links show the screenshots of the DB Code Generator Wizard:
- DB Code’s Main tab
In this view there are some central settings that need to be configured. When clicking on the ‘Create Procedure’ button a complete VBA function is created which retrieve the data from the database.
- SQL Query’s tab
In this view new SQL queries can be created and tested and when clicking on the ‘Test’ button a new tab is viewed with the output of the query.
- Parameter’s tab
In case of using parameters for the queries these are controled in this view.
- Setting’s tab
Here are the general databases and QueryTables settings handled.
- Connection’s tab
Here You can administrative the available connection strings.
- SQL tab
In this view You can administrative the configured SQL expressions.
In addition to the above it also offer another utility, Code Snipper, which allows developers to store complete procedures as well as snippet code. Saving and using the code will be available via a toolbar in the VB-editor.
All information is stored in a local Microsoft Database (so called ‘Access’ database).
It can be used with most of the common databases. However, one idea I has is to implement stored procedures but it will then only target SQL Server 2000 / 2005.
If it will be re-created it will be developed with VB.NET 2005 and distributed as freeware.
The following requirements must be met in order to use it:
- .NET Framework 2.0 or 3.0 (depending on when it’s released).
- Excel versions 2003 or 2007.
Let me know what You think about it from a general view. More specific, if it interesting to take part of the development via the blog or not. Also if something is missing which You would like to see as part of the utility.
Ps. In my next post (next week) I will introduce the case that will be used for creating a utility for Excel from VBA to VSTO.