wraith, this is something I have been thinking about also. You mentioned giving MS Access a go, and I'm in that phase right now. What did you feel was disappointing about Access?
-superboyac
1. The need for some sort of access runtime
2. The use of SQL that is different from T-SQL, which I am used to
3. The efficiency in large database operations
4. The lack of support for triggers, stored procedures, and functions
5. The lack of ability to use SQL CLR procedures/functions
In short, VistaDB is limiting in some ways next to SQL Server, but Access is limited in almost every way next to SQL Server. As Renegade says, it's a valid option in the limits of what it's built for. But building custom applications, I find myself too often limited by it, and I
really don't want to do a full scale installation just because I'm using a database.
<snip />
EDIT: or, as you mention, you might be able to do it with a recursive CTE, but that's (a) nonstandard SQL, and (B) non-supported here anyway.
<snip />
Anyway, thanks for this review. I've considered VistaDB, so seeing a step-by-step in-depth review is very interesting to me.
-CWuestefeld
Yeah... I use that bit of code (or something similar) to do this in SQL server, so I can do it there, and because this is just *so* close to SQL Server, not having it was a bit more jarring than not seeing that facility in Access, for example. The penalties of expectation, because everything else so far is *so* good.
And thanks for the suggestions/feedback. If there's anything in particular you're interested in, let me know!