Jim, A few last comments...

I have enjoyed reading this thread, all the opinions - different ones do help us all understand, more about the VFP and where is belongs.


<snip> "grow up, and seriously compete with true enterprise level apps".

Without a server, the native flat file technology used in VFP keeps the our applicaitons as lan products. In order to write for a 'Enterprise' server wan technology needs to be deployed... IMO all too often, people think of VFP as a Lan only , destop app, becuase it is not connected to server, Sure there are work arrounds,. but the impression is that its nothing more than a Access database,.. But used by the old xbasers... Not that is not mature, but just that it not enhearently Client Server. and thus shoudln't be considered for Wan / or large scale applications. (all totally incorrect) but the your thought is SO right, that IF vfp had some sort of server module, it would indeed help overcome those comments. as you know, the impressions are what turns the wheels of business, not absolute knowldge. If the impression changed and VFP had a Client Server engine. Well I think that would change many impressions. ,,,Like I said, thats just my opinion.


The details of the pricing of a server module would be worked out.,, limited user for one price, Site licence for another price etc... lets not let that be any source of static.


I love this track... the more I read it, the more it makes sense, at least to me.


>>Bob Lee