Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • His last point was grammatically incorrect; I could not understand his original meaning. I guessed, and I may have guessed wrong, so he may not have meant that he was unfamiliar with Visual FoxPro. Commented Apr 5, 2012 at 21:59
  • About FoxPro, my question was edited. I said that is a verbose language and for me, this is not good, but it's a personal opinion. I understand it, but I don't like, and the main point is the age of language. It was not updated in my company, but there are new releases (Visual FoxPro 9 from 2007). Commented Apr 6, 2012 at 3:05
  • 3
    @RenatoDinhaniConceição, it is common not to upgrade a database product as upgrades break things that currently work and there is no money or time to spend to make changes you don't need to if you maintain the older version. This is a business choice. Commented Apr 6, 2012 at 14:09
  • @HLGEM I think most languages have backward compatibility. Is about using the most recent version, not changing the language. Commented Apr 6, 2012 at 14:14
  • 1
    @renato, most database applications are not easily backward compatible. Commented Apr 6, 2012 at 14:45