Good Morning Leland
We have a few people in our sub Open Source Backend to VFP front camp ! Paul McNett, Jerry Krebs, Jason Bradley Nance, just to name a few.

Now what it interesting to me, and I am begining to see light, is not only the ability to code to a Mysql Server, but what about writing generic enough code, which works with Mysql, Postgresql, DB2 and ...

Here is where I am going with this.

The selection of a database for a company is many times more complex and convulated then the selection of a user interface.
Some Companies require the use of Oracle, Others pure M$ only shops require the use of M$Sql. By writing to one backend, I think we are seriously hindering the ability of VFP (not becuase Postgresql is better) or Mysql can handle large tables, or Oracle can handle on line data replication and file resizing, or DB2 is the only database my company will allow on my server... and so on and so on.

So if our are matured to remove one vendors use of a non standard SQL statment, while there might be performance hit, The VFP apps we develop would be able to run on just about any companies chosen platform, accessing their large database's directly, (like the customer or client ) or whatever the largest part of the system is, without replication into Mysql Postgresql, or whatever .

The way I am thinking these days about VFP is that is strength is in beautiful the UI and native way of handing data centric forms, and so on.

All that being said, Ill say this, If I started with Postgresql, I would be staying with it... The only reason I ended up with Mysql, is I saw the waves of acceptance for the Mysql platform, and the use by ISP's. It was and still is fast becoming the standard ISP datbase platoform. and a year ago, I started feeling out of touch with the datbase community (not VFP's) but the overall database community and needed to find out for MySelf what all the Hoopla was about MySql - What was so big a story about Client/Server What was I missing developing app's which were File based as apposed to Server based.

IMO if I were you, I would stay with Postgresql, It has featues NOW which MySql in the future will maybe someday catch up with. But why would you trade in a Porsche for a Mazda ? Because more people own Mazda'a Both Run, Both Run Solid, They both will get you speeding Tickets.

You the driver, just rambling here, should develop your driving skills to be able to drive either the porsche or mazda Without knowldge of what one you are in. That makes you 10 time more valuable !

Bob Lee






>Hi Bob Lee,
>
>I like the new UT interface. I really hadn't given the limitations of the linux, Window, and Unix file systems any thought. Given the popularity of MySQL within the VFP community, I may have to reconsider using postgres as my backend server, since I really need to flow with the tide of current opinions.