>>>>>>>Out of curiosity, how come you did not choose some other (manly) men name but rather concealed your identity as female online ?
>>>>>>>
>>>>>>>You never made any single mistake as to reveal your real gender. If you did not come up like this, I would forever refer to you in my mind as 'that nice German Lady that knows hell of a lot of FoxPro' :))
>>>>>>>
>>>>>>>And BTW Welcome back, any name you ever choose to use :)
>>>>>>
>>>>>>Hi,
>>>>>>
>>>>>>
>>>>>>I'm here but limited, the Fox will go out of my focus soon. I'm looking around for something new to set up the old projects. Not realy shure what to use except to move away from Redmont.
>>>>>>
>>>>>
>>>>>I look around as well, just can't seem to find anything even remotely applicable for my use cases.
>>>>>There are few things emerging out there (like for instance AlaskaSoftware or Servoy), but for what we need
>>>>>VFP9 is still ultimate solution. :)
>>>>>
>>>>>My (as usually controversial {g}) theory is that at this point VFP9 usefulness is biggest reason why we do not already have
>>>>>multiple tools/languages of similar characteristics sprawling around. Smart Redmond. In a way they got rid of VFP, but by making it (VFP9 especially) so good, they made it very difficult for any competition to come close / overtake.
>>>>>
>>>>>VFP9 is simply to good to let go. In a way It is both blessing and the curse. I am not sure what would happen if M$ created
>>>>>major environment problems for VFP9 apps in some future OS version, but I have to bet that they will be as responsible as they were so far. Weather we like them or not, their track record for backward compatibility is quiet good. Besides, FoxPro apps are running literally everywhere (Fox DOS apps are not only still running but still selling !! ), so I don't believe it would be in their best interest to create way to many problems to way to many people.
>>>>>It is just not done by any serious business, so it is very unlikely to be done by M$.
>>>>>
>>>>>I can easily foresee VFP9 running (and me using it) for next 20 years if not more. :)
>>>>
>>>>I think on apps that run for over a decade now. I see the way VFP stumbles behind all the time (remember how much time we need to get UNC paths for example) and the problems we encounter more and more with newer systems (printer environ, file systems for example) I realy like VFP, and will keep a copy for some small tasks the next decades, but it smells.
>>>>Need something better scalable. I deal with big company, so I have to have some marketing idea about the lang. And VF what sounds for more then a decade in my ears and if they ask how long M$ support will run what answer do I have??
>>>>Customer decides to move. Will be happy if I move to, even let me decide about lang., but if I stuck on VFP there is no further question.
>>>
>>>
>>>I understand this perfectly well. If you are chasing app market especially big corporate and/or state market then VFP is defenetely
>>>no longer horse to ride. For that matter it never was the case. For SME's however, I don't subscribe to 'official' recommendations.
>>>If you have business that it's whole value (investment) is for instance 1mil usd, expecting yearly return of let say 100 000 usd
>>>and you want it done ASAP, then most of mainstream mantra (WEB / NET / MSSQL road) is big bunch of (extremely expensive) bananas. Technology needed might very well become cost/time prohibitive.
>>>
>>>Official Redmond mantra nowdays say 'All new apps should be WEB based / preferably NET MSSQL '
>>>To me that pretty much sounds like; 'People should only eat at restaurants'.
>>>While this might be applicable for some people, hunger happens all over the place {g} , while food that makes us through the day is most of the time everything else but the restaurant food. People make apps using whatever suit them best. Whatever is cheaper, faster (not neccesarilly better) provided that it can do the job. Just like in that old Chineese proverb; 'It does not matter what color is the cat ...'
>>>
>>>I do not care what color is the cat, for as long as it is as smart and as fast as our old Fox is ;)
>>>Just that I did not see such a cat just yet :)
>>
>>There is not much left to say, isn't it?
>>Redmont was the last try. Now I try something else. The SERVOY idea seems not to bad for its scalability to the front end back end. If you show a customer the integration on its PC and in the same moment on his rotten fruit he will be impressed. Believe me.
>>O.K. we will not get it as cheap as the FOX. But otoh price and licensing modell of the fox rise not much interest in a company that is develpoing it, especially if the comp owns better cows. This I can understand.
>
>I would have gladly paid licencing fees for FoxPro databases! If they were to provide better FoxPro databases!. Like erase 2gb limit,
>make it more robust, limit the ways to write into it so that mythical 'corruption' indeed never happens etc. To bad this was not considered and instead we got worst outcome ;-/ (VFP dropped all together)

That is called SQL Server. You can still write VFP apps using it and eventually port them to a different front end if needed.

>
>As for Alaska, and especially Servoy, perhaps more business scale intuitive licencing model (which translate to _MuchCheaper!!!_ for smaller businesses) could gain them lot of ground at this point in time. (This is a business opportunity time window for them)
>Otherwise our old beloved Foxy will be (rightfully) chewing on their chickens forever.
>
>Is it better to collect 1k yearly from 1M+ customers or collect 20k from 20k+ customers ?
>I am not that good with math, so if I was new database vendor I would perhaps choose second option as better. Hey.. You get 20K from each customer ! That is not that bad right ? {g}
>
>But that is only old greedy me! ;-P ; New Xbase/Database vendors are perhaps bright people surely better with math. :)
>
>Cheers & Have great weekend :)
>