>Yes but that was way before the time we learned to code in layers. At least let me have the same database, Data objects and Bizz objects... irregardless >of what the platform is.

Most frameworks today support different database engines (Postgres, MariaDB, MsSQL, Oracle, etc..). Platforms that might be different. MsSQL only runs on windows - but I believe the 'free' Postgres, Firebird and MariaDB run on windows, Mac's and Linux servers. Oracle on windows and LInux.

So I guess if you want a database engine to run cross platform you're stuck with the 'free' versions of Postgres, Firebird and MariaDB.

So which is it - you want cross platform databases or you want 'not free'?

Open source databases are tools.

My obvious point here - 'open source' or 'free' tools are not a PIA to use or work with today. They continue to improve daily and that includes programming tools/frameworks. And what you describe as incomplete tools with bugs and to difficult to work with (my description of what you said) I don't agree with.

In Foxes hay days companies like SBT, AccountMate and others had to design their own frameworks with work arounds/fixes to VFP's framework. So I do not see any different between FOX and other open source projects (except money). I designed my classes in Fox and today I design my class in python. What's the diff? Fox is dead and python is growing.

Oh there was a GUI designer, the data access, etc.. The same things are in the python (I don't use the GUI designer because I don't want to not because it doesn't work). Local access to data - got it. Nice GUI controls - got it. I have access to all the database engines including the new NOSQL's. So my open source and free programming tools aren't too bad.

Are there bugs - sure but everything has bugs.
Johnf