On Friday 02 July 2010 08:19:24 pm bob gailer wrote: > On 7/2/2010 5:56 PM, Jeff Johnson wrote: > > [snip] > > > > Visual FoxPro ... is very similar to Access > > I differ. Access and FoxPro are very different. Yes they both use > tables, relationships, indexes and SQL. Yes they both have visual > designers for forms and reports. Yes they both are programmable. > > But the differences are much more dramatic than the commonalities. I > have developed in both. I find it painful to work in one while desiring > a feature that exists only in the other.
Yes I agree (0ver 20 years with Fox/dBase) they are different. I'd say Access provides several no thinking tools for the end user where VFP requires a little more effort. But the concepts of both are very close. The underlying code is also very different in that I find VFP 10 times easier when working with data. That said, the question at hand is does Dabo make a good fit for the poster. I'd say without question the answer is yes. Yes it is true that Dabo follows VFP more closely than Access. But if the poster is moving from Access to a python solution does it matter? The poster is making a change to a new language which is a major change. At least Dabo keeps many of the concepts a Access user already understands. Therefore he/she will be more productive. Johnf _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor
