locked
Future of Visual FoxPro RRS feed

  • Question

  • What is the Future of  Visual FoxPro ??

     

     


    Ahsan
    Friday, March 25, 2011 11:28 AM

Answers

  • You should not ask about VFPs future, because VFP will have its place for many years to come.

    You should ask about your future and this may depend on your VFP knowledge and what you want to accomplish.

    If you are new to VFP then IMHO it might not be the best idea, to start with the fox as a new tool. However, if you have used this language for some time now and you do not want to start with a new language (for whatever reason), then you will have fun with VFP for a long time.

    Me, for my part, I am pretty sure, that I ( as an oldie in years and VFP ;-) ) will use VFP for 5 to 10 more years (maybe even longer). However, our newbies/apprentices will use other, cloud oriented languages.

    Some time ago I posted some (not complete) lists with blogs and sites all around VFP, where you gain lots of ideas, code, tools and apps that will make your life as VFP programmer a whole lot  easier:

    http://tomsvfpblog.blogspot.com/2010/08/visual-foxpro-blogs.html

    http://tomsvfpblog.blogspot.com/2010/07/links-zu-visual-foxpro-im-web-links.html

    http://tomsvfpblog.blogspot.com/2010/09/visual-foxpro-links-reloaded.html

     


    Gruss / Best regards -Tom 010101100100011001010000011110000101001001101111011000110110101101110011
    Friday, March 25, 2011 12:48 PM
    Answerer
  • Bright.
    dni
    Friday, March 25, 2011 12:07 PM
  • If you look around and count applications which are still running under VFP 6 or even FoxPro 2.6 then you should not be afraid of VFP 9 future for at least 10 or 15 next years... Did you even notice Microsoft is not supporting VFP? Visual FoxPro will still be here and the community will support it as of today.

    And we may suppose some 3rd party company coming with compatible product sooner or later because FoxPro is still the World best desktop database product and the pool of running applications is large. And it is valid even when many voices are whispering "Cloud, cloud, cloud, ..." today.

    OTOH, you may decide .NET is better because customers are paying as twice as much and the development time is also double comparing to VFP app development time.  .NET is better for web applications in fact but not for desktop apps.

    You could also ask about the future of programming... AI will beat all programmers because to implement exact specification (and what else is database programming?) will be a question of seconds.

    Friday, March 25, 2011 12:08 PM
  • As a light weight, less bloated alternative to .NET!

    On 64-bit, I recently came across this:

    "From http://blogs.msdn.com/b/rmbyers/archive/2009/06/08/anycpu-exes-are-usually-more-trouble-then-they-re-worth.aspx

    1. 32-bit tends to be faster anyway
      When an application can run fine either in 32-bit or 64-bit mode, the 32-bit mode tends to be a little faster.  Larger pointers means more memory and cache consumption, and the number of bytes of CPU cache available is the same for both 32-bit and 64-bit processes.  Of course the WOW layer does add some overhead, but the performance numbers I've seen indicate that in most real-world scenarios running in the WOW is faster than running as a native 64-bit process"

    On Cloud Computing, you can run VFP in the cloud right now:

    Cloud Web Hosting

    Don't believe a lot of the Hype and FUD coming from MS and the cheerleaders.


    Claude Fox - http://www.codeplex.com/activevfp - Open Source VFP web development
    Friday, March 25, 2011 2:33 PM
  • There's no reason not to use VFP, it's written in C a native OS language and it's open source (all but the core engine). It won't ever stop working and as Claude mentioned 32-bit apps run faster than 64-bit apps anyway. There's really no other development platform out there that has a full blown programming language, database, forms and reporting engine built in in a single product. There was a reason why MS purchased and developed Fox anyway. The technology that is in the Fox core is still very relevant otherwise MS would release it to the community too.

     

     

    Saturday, March 26, 2011 6:35 PM
  • Stephen,

    Yes, that is possible, but highly unlikely for a couple of reasons:

    - It would also break thousands of other applications

    but, Microsoft could do that.

    - Virtualization. IMO, virtualized XP will be around a long time. Microsoft could change Windows and provide a type virtualized XP on every machine for backward compatability.

    Also, 64 bit OS causes a few issues with VFP apps. And, 64 bit is becoming the norm on new machines now.


    Craig Berntson
    MCSD, Visual C# MVP
    INETA Community Speaker
    www.craigberntson.com
    Tuesday, March 29, 2011 3:26 PM

All replies

  • Bright.
    dni
    Friday, March 25, 2011 12:07 PM
  • If you look around and count applications which are still running under VFP 6 or even FoxPro 2.6 then you should not be afraid of VFP 9 future for at least 10 or 15 next years... Did you even notice Microsoft is not supporting VFP? Visual FoxPro will still be here and the community will support it as of today.

    And we may suppose some 3rd party company coming with compatible product sooner or later because FoxPro is still the World best desktop database product and the pool of running applications is large. And it is valid even when many voices are whispering "Cloud, cloud, cloud, ..." today.

    OTOH, you may decide .NET is better because customers are paying as twice as much and the development time is also double comparing to VFP app development time.  .NET is better for web applications in fact but not for desktop apps.

    You could also ask about the future of programming... AI will beat all programmers because to implement exact specification (and what else is database programming?) will be a question of seconds.

    Friday, March 25, 2011 12:08 PM
  • You should not ask about VFPs future, because VFP will have its place for many years to come.

    You should ask about your future and this may depend on your VFP knowledge and what you want to accomplish.

    If you are new to VFP then IMHO it might not be the best idea, to start with the fox as a new tool. However, if you have used this language for some time now and you do not want to start with a new language (for whatever reason), then you will have fun with VFP for a long time.

    Me, for my part, I am pretty sure, that I ( as an oldie in years and VFP ;-) ) will use VFP for 5 to 10 more years (maybe even longer). However, our newbies/apprentices will use other, cloud oriented languages.

    Some time ago I posted some (not complete) lists with blogs and sites all around VFP, where you gain lots of ideas, code, tools and apps that will make your life as VFP programmer a whole lot  easier:

    http://tomsvfpblog.blogspot.com/2010/08/visual-foxpro-blogs.html

    http://tomsvfpblog.blogspot.com/2010/07/links-zu-visual-foxpro-im-web-links.html

    http://tomsvfpblog.blogspot.com/2010/09/visual-foxpro-links-reloaded.html

     


    Gruss / Best regards -Tom 010101100100011001010000011110000101001001101111011000110110101101110011
    Friday, March 25, 2011 12:48 PM
    Answerer
  • As a light weight, less bloated alternative to .NET!

    On 64-bit, I recently came across this:

    "From http://blogs.msdn.com/b/rmbyers/archive/2009/06/08/anycpu-exes-are-usually-more-trouble-then-they-re-worth.aspx

    1. 32-bit tends to be faster anyway
      When an application can run fine either in 32-bit or 64-bit mode, the 32-bit mode tends to be a little faster.  Larger pointers means more memory and cache consumption, and the number of bytes of CPU cache available is the same for both 32-bit and 64-bit processes.  Of course the WOW layer does add some overhead, but the performance numbers I've seen indicate that in most real-world scenarios running in the WOW is faster than running as a native 64-bit process"

    On Cloud Computing, you can run VFP in the cloud right now:

    Cloud Web Hosting

    Don't believe a lot of the Hype and FUD coming from MS and the cheerleaders.


    Claude Fox - http://www.codeplex.com/activevfp - Open Source VFP web development
    Friday, March 25, 2011 2:33 PM
  • There's no reason not to use VFP, it's written in C a native OS language and it's open source (all but the core engine). It won't ever stop working and as Claude mentioned 32-bit apps run faster than 64-bit apps anyway. There's really no other development platform out there that has a full blown programming language, database, forms and reporting engine built in in a single product. There was a reason why MS purchased and developed Fox anyway. The technology that is in the Fox core is still very relevant otherwise MS would release it to the community too.

     

     

    Saturday, March 26, 2011 6:35 PM
  • As a 60-yr old long in the tooth with various flavours of vfp I believe it will see me out so I am not too worried - EXCEPT if Microsoft release a version of Windows that is suddenly incompatbile with vfp. Any chance of that ??

     


    Stephen Ibbs
    Tuesday, March 29, 2011 12:24 PM
  • Stephen,

    Yes, that is possible, but highly unlikely for a couple of reasons:

    - It would also break thousands of other applications

    but, Microsoft could do that.

    - Virtualization. IMO, virtualized XP will be around a long time. Microsoft could change Windows and provide a type virtualized XP on every machine for backward compatability.

    Also, 64 bit OS causes a few issues with VFP apps. And, 64 bit is becoming the norm on new machines now.


    Craig Berntson
    MCSD, Visual C# MVP
    INETA Community Speaker
    www.craigberntson.com
    Tuesday, March 29, 2011 3:26 PM
  • Hi Craig,

    Can you give us some heads up on problems that we may encounter with 64-bit OS?


    Mike z
    Wednesday, March 30, 2011 1:09 AM
  • As a 60-yr old long in the tooth with various flavours of vfp I believe it will see me out so I am not too worried - EXCEPT if Microsoft release a version of Windows that is suddenly incompatbile with vfp. Any chance of that ??

     


    Stephen Ibbs
    I doubt it since so much runs in a 32-bit environment now and for many applications is actually faster that way.  And even if there was an issue, there would pretty immediately be a workaround from the VFP community.  So my guess is this stuff is safe for the foreseeable future.  VFP, PHP, even VB6 and others, no doubt, are good alternatives for those not wanting the bloat and about-faces that come with using .NET.  IMO you're more likely to face compatibility issues staying on Microsoft's bleeding edge than staying with the stability of VFP.  Everything else is FUD...   Smaller and lighter is better in today's world and that ain't .NET

    Claude Fox - http://www.codeplex.com/activevfp - Open Source VFP web development
    Wednesday, March 30, 2011 8:13 AM
  • You need to be careful with ActiveX controls. Make sure they register as 32 bit

    You'll need 64 bit ODBC drivers if you need ODBC access


    Craig Berntson
    MCSD, Visual C# MVP
    INETA Community Speaker
    www.craigberntson.com
    Wednesday, March 30, 2011 2:36 PM
  • You'll need 64 bit ODBC drivers if you need ODBC access

    But this is not VFP problem... :-)

     

    Wednesday, March 30, 2011 6:57 PM
  • Hi Ahsan,

     

    Thanks for posting in the MSDN Forum.

     

    Any update? I have marked their reply as answer, if you think it provides no help, please unmark it.

     

    Thank you for your understanding and support.

     

    Best Regards,


    Mike Feng [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Tuesday, April 5, 2011 8:38 AM
  • You should not ask about VFPs future, because VFP will have its place for many years to come.

    You should ask about your future and this may depend on your VFP knowledge and what you want to accomplish.

    If you are new to VFP then IMHO it might not be the best idea, to start with the fox as a new tool. However, if you have used this language for some time now and you do not want to start with a new language (for whatever reason), then you will have fun with VFP for a long time.

    Me, for my part, I am pretty sure, that I ( as an oldie in years and VFP ;-) ) will use VFP for 5 to 10 more years (maybe even longer). However, our newbies/apprentices will use other, cloud oriented languages.

    Some time ago I posted some (not complete) lists with blogs and sites all around VFP, where you gain lots of ideas, code, tools and apps that will make your life as VFP programmer a whole lot  easier:

    http://tomsvfpblog.blogspot.com/2010/08/visual-foxpro-blogs.html

    http://tomsvfpblog.blogspot.com/2010/07/links-zu-visual-foxpro-im-web-links.html

    http://tomsvfpblog.blogspot.com/2010/09/visual-foxpro-links-reloaded.html

     


    Gruss / Best regards -Tom 010101100100011001010000011110000101001001101111011000110110101101110011

    Thank you so much for your support to Foxpro programmers. God bless your heart.
    Monday, April 11, 2011 2:32 AM
  • This is very encouraging.  I am still using VFP 6.

    Thank you for so much for your contribution to our community.

    May The Lord provide everything you need in life.

    God is Good

     

    Monday, April 11, 2011 2:34 AM