>Now, if you have created it, this is because you have found some things that needed to be enhanced in a regular blog engine. Could you elaborate more on those issues?

You mentioned that your engine uses SQL Server as the data engine. What data engine the mentioned product in your original message uses?

Personally, I don't see a big deal with blogs. From what I have seen so far, except for a few entries where we can find good technical materials, most of them are mostly personal journal such as "look at my pictures of the last trip", "what this movie", etc. From my research since a month, I have found that looking for information, obtaining report, finding my way into these blogs, was extremely difficult. The XML feed seems to be the biggest nice issue. But, the interface is extremely different from one site to another. When our client first recommended that we use a blog engine, I was hesitating on this. With all the complications that we will face just to deliver the first phase, we would end up much better to do our regular database stuff on the Web such as using WWC with VFP and/or SQL Server for example, with some .NET here and there.

The original product also uses SQL.

I found the same problem as you with blogs... Most of the information is personal in nature, with only a small portion being useful. That is where I focused on improvement. The Better Log application I wrote allows one to select a category for the entries they make (which can later be searched upon). Also, the person making the entry can assign keywords to the entry for the purpose of searching. The traditional blog engine does not support searching... The Better Log application offers extensive search on a number of different criteria. I have also included a number of flags (source code included, examples included, etc...) that can be used on the search screen. More than anything I tried to make the Better Log more useful as far delivering information.