B3d or BMax for DBAse app ?

I've had recent experience with relational databases in Access... and I wanted to develop some database queries through either BMax or B3d, not necessarily on access (however it's the only DBase I've worked with to date) - what are the pros / cons of both (i.e. BMax or B3D) ? I'm most familiar with BMax but am prepared to delve back into B3D for a DBase module.

Brucey has a fully working ODBC driver module for BlitzMAX. Blitz3D, not so much.

The database module is done in such a way as you can use the same program code and change to a different database without much effort. (See my sig for a list of databases covered).

ODBC lets you use *any* database that you can get ODBC drivers for, so that opens up a whole load of others I haven't built a specific module for.

I'd also like to add drivers for Oracle, DB2, Informix and some others in the future, if I get some time to play.

"Do you really want to use Access or can it also be a real database?" We used to say that at Datatrak, a company I've worked for a couple of years ago, and it's true. Access is BY FAR the worst piece of crap Microsoft has ever published. Well, not necessarily Access itself but rather the notorious "Jet" engine that it uses. Unstable, unreliable and crashes the "database" almost daily (yes, that is first hand experience, no hear-say).

Microsoft's FoxPro stuff is pretty good, though, and also their MSDE and SQL Server are very usable (even though I do not necessarily like the T-SQL dialect). Maybe that's because they did not invent those themselves but bought them.

If you go .NET, my recommendation for an embedded database is VistaDB.

As for BlitzMax, my choice for an embedded engine would be SQLite, either through Brucey's module or alternatively through SQLiter and Teamonkey's module.

Thanks for the advice, I will give SQLite through Brucey's module a go.

If you're going with a fully fledged relation database that uses SQL - go for Postgres.