>>Yes I know but we were talking about a single environment to write code for. In this case you;re back to using a server backend to writing code in a different language (PHP in your case).

Fair enough. In our case, the php part is limited to database-agnostic data manipulation and queries which look fairly obvious in PHP. Jquery does all the rest including drag-drop in grids, table-driven field validation and an equivalent to the VFP browse against giant tables using lazy loads/saves. We use SQLite to mimic the infamous giant persistent VFP cursor. Users can add/edit a 1-M resultset with no server roundtrips until they're done. If you use NET for similar purpose, you may end up with equally distinct mechanisms. ;-)

>>BTW, I didn't realize Chrome/WebKit had a built-in version of SQLite! That is interesting for sure, although building complex logic with aysnchronous SQL calls is far from pleasant :-) Thanks for the pointer!

I know, SQLite turns up almost everywhere now. It's the default on Android, Mozilla, you name it. It has some secret clever features as well once you drill into it- e.g. you can ignore the stated maximum sizes, easy enough to grow a database to terabytes once you know how (and if the device has room!) But it's still fine to access a database on a memory stick if you need to.