Ok, people asked for a long time to have VistaDB support. Now, the database' metadata is easy to read, except perhaps the unique constraints, so that's not the problem.

The problem is VistaDB itself. It lacks: - RIGHT joins - WHERE EXIST(... - paging method.

now, RIGHT joins are important, as LLBLGenPro sometimes changes LEFT joins into RIGHT joins because it's required for the relations specified. This can lead to problems at runtime. WHERE EXIST (..) is required for UPDATE / DELETE statements with a filter on another entity, as VistaDB doesn't support DELETE FROM FROM or UPDATE... FROM etc.

There's also no way to fetch paged data, so client-side paging is required, like access.

All in all, this db isn't up to par, and will give problems, especially the right join absence (who releases a database engine without right join support?). Also non-ansi joins can't be used as it doesn't support (+) or (*) column suffixes.

On monday I'll start on CF code which should be pretty straight forward, and after that on the VistaDB code. However I've the feeling it's not something worth spending time on for now. So I'll give it a try, but it if sucks in the end, ask VistaDB for better SQL support

Ok, I asked VistaDB when RightJoins were added... and what did I get back? "RIGHT joins aren't supported". Yes I knew that already.

It WILL give a lot of problems for our customers who will use VistaDB, so I'll drop VistaDB support for now. People who want / need an embedded database with a low-memory footprint, check out Firebird Embedded.

We havea client application that uses an access back end on the client. Once installed, it works fine on the client, but there are a lot of hoops to jump through for installation. And Microsoft is not making it any easier ( I assume they are pushing people to use MSDE instead). I was hoping that VistaDB would be a good alternative, but now I have to reconsider based on this thread.

If I go from Access to Firebird should there be any performance penalty? We tried just a test run about 6 months ago and I thought it felt much slower. Does anyone have experiance going from Access to Firebird on a client side application that can share any insights?

John wrote:

We havea client application that uses an access back end on the client. Once installed, it works fine on the client, but there are a lot of hoops to jump through for installation. And Microsoft is not making it any easier ( I assume they are pushing people to use MSDE instead). I was hoping that VistaDB would be a good alternative, but now I have to reconsider based on this thread.

Looked at SqlServer 2005 express? It's easier to install.

If I go from Access to Firebird should there be any performance penalty? We tried just a test run about 6 months ago and I thought it felt much slower. Does anyone have experiance going from Access to Firebird on a client side application that can share any insights?

Firebird is a much more mature database than access is though with a client-app, e.g.: an app which uses a single db in single user mode, you won't notice it that much. If you want to leave access, firebird is a good alternative. And free.

The point is that VistaDB never would be the alternative you'd like to have: it has less features than access has.

Hi,

Did you see the features in the new VistaDB 3.0

http://www.vistadb.com/features.asp

Maybe this version has the features required by LLBLGEN.

Best Regards Gianfranco

ggpnet wrote:

Hi,

Did you see the features in the new VistaDB 3.0

http://www.vistadb.com/features.asp

Maybe this version has the features required by LLBLGEN.

Best Regards Gianfranco

Yes I saw it, it still doesn't support RIGHT JOINs and EXIST queries. VistaDB therefore won't be supported. Frankly I also don't find it an appealing db to support. If another db should be supported, it should be SqlLite, which does the same thing as VistaDB and is free.

If another db should be supported, it should be SqlLite,

Or Foxpro!

arschr wrote:

If another db should be supported, it should be SqlLite,

Or Foxpro!

A 3rd party developer has already made templates and a driver for foxpro Check the subversion repository:

svn://www.sd.nl/LLBLGenPro/CustomDrivers

That code isn't for v2.0 yet, he's working on that. You'll also find an informix driver there (2 actually)