Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Visual Foxpro or Visual Basic
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00104962
Message ID:
00104969
Views:
25
Re:
>BTW, If you have a lot to do with data... VFP is the way to go.
>
>>I will develope a new application.
>>The data will be in a Sql database.
>>What are de benefits of using Visual Foxpro instead of Visual Basic??
--

Greetings FoxHounds (hmmm?),

Microsoft has a 37 page White paper called "Choosing the Right Database Tool."
It is available on the Microsoft.com/vfoxpro/ site in the owners area. This
White Paper describes and compares features of VFP 5.0, VB 5.0 and Access.

The two tables in the document list side by side the relative features of each.

Despite the popularity and improvement I see going on in the VFP world, VB
continues to Kick us where it hurts. And the relative instability of VFP
data tables and indexes vis-a-vis the client server and .mdb alternatives
don't help.

The 800 or so database handling specific functions and commands in VFP are
probably the biggest competative advantage against VB.

You can look at White papers on products to get an idea. Visual AccountMate
had a White Paper on the Microsoft site a while ago extolling the benefits
of VFP development. It stated (as I recall from two years ago) that their team
estimated that the process of bringing Visual AccountMate into a 32 bit
Windows-95/NT environment would have taken twice as long in VB as it took in VFP.

Conversely, go out to Solomon Accounting's WEB site. Their site extolls to
no end the wonders that their team encountered when they converted Solomon Accounting into a VB application. They even have a VB based customization toolkit.

Still, in the Microsoft White Papers, I see no great role being laid out for
VFP in the pantheon of Visual Studio Components. In Microsoft's three-tier
architectual approach, VFP apparently gets stuck in the middle tier. In the real world, it looks like VFP can hand the front end also, leaving the stable
back ends to MS SQL Server. But those are solutions we must push to create
successfully in order for the world of our clients to stay on board with VFP.

Anyway, that's my input.

I would like to know if anyone has presentable documentation regarding the
relative instability of .dbf tables and index files, especially as this problem
relates to unprotected power supplies.

Thanks.

- Chuck
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform