>128-bit OS won't be commonly available for at least 20-30 years, that's my prediction. Too little profit both money wise and performance wise, way too high cost.
Plus - there's no need.
We switched to 64 bit processors mainly because of the added ability to access memory beyond 2 gigabytes that was starting to become a problem for server apps. 64 bit can address 16 exbibytes (whatever that is :-))
64 bit computingI don't think we're going to hit the limits of that anytime soon even in the server room :-)
+++ Rick ---
>
>>Perhaps there is something about:
>>* Essentially "dead" -- no more development, no more support from Microsoft
>>* Stuck in 32-bit (unless someone implements the entire engine in 64-bit) -- though 32-bit software does run today, it's a "2nd-class citizen" in that it requires an emulation layer to operate (i.e. doesn't run "native"). Essentially VFP is in the same status that FPW was in back when 32-bit OS became the norm. Don't be surprised when 128-bit OS comes around and 32-bit support gets dropped.
>>* These points could be a "dealbreaker" with customers.
>>
>>If it's an update of an existing software then you could probably get away with sticking with VFP -- for a new product it's probably not such a good idea.
>>
>>>Ouch. Do you mean people think of VFP as dated or do you mean its abilities are not up to modern snuff?
>>>
>>>>>As I come kicking and screaming into the current century, is is possible to generate text messages to users through a VFP app?
>>>>
>>>>If you're coming into the current century, you won't be looking at a solution in VFP....