Hi,

I'm just a .NET Developer, but I find myself working with databases more and more these days as I'm doing some migration from a legacy system to our newer stuff.

I've found this tool to be good, but not great. I didn't expect that it would be great, because it's free but it's certainly helped me a lot.

I have found that it doesn't work out intellisense in some places where I'd expect it should, but I'd imagine that's where version 3.0 will fill in the hole.

I'm very tempted to buy 3.0 now for $99 but is there a list of what doesn't work in 2.0 that will work in 3.0?

Why do you say that? What exactly doesn't work? I've found it works in most places, missing a few irritating things (like picking up new tables, or when using 3-part naming).

Before you judge version 3, remember that they bought version 2 from another company, didn't feel that it was worth selling and are completely rewriting it. Version 3 isn't going to be a modificiation to version 2, it's giong to be a complete re-do.

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Thank you, thank you, thank you for being so candid about this product and your plans for the new version.  It's not often we find out the 'real deal' on software and I have to say, it was very refreshing.   

I started using v2 a few weeks ago and although it's not perfect, I really like it.  Hey, it's a lot better than what we had before.     I will definitely be purchasing v3 when it's available.  As an instructor, I am telling all my students about your product and I will pass on the information about v2/v3. 

Jen