Jamuna,

>> Has anyone used Powerbuilder? I'd really like to know how it compares to VFP ? And what you can do with VFP that you cannot with Powerbuilder? I need to be able to prove that VFP is better than anything else presently out there....

I started w/ PB 2.0 years ago, used 3.0 and 4.0 for several years, and just recently got 5.0, but haven't done much with it yet.

To point out some of PBs benefits, (playing the devils advocate <s>)

>I do not know about Power Builder but with VFP ...
>
>1. VFP is inexpensive.

Very true.

>2. You do not need to go C/S if the project does not require it.

True, thou SQL Anywhere is packaged w/ PB, which provides a very easy
way to develop locally and switch to SQL Server.

>3. The database engine is very fast, flexible and easy to use.

I've found VFPs db a pain to deal with at times, with Deleted records especially. For someone with an x-base background not a problem, but with a SQL background the concept of "deleted" records remaining in a table is foreign.

>4. Maintenance of a system in production is very easy, because you have
>immediate access to the tables, in the same environment.

With PB, you can create/alter tables in a SQL db from within PB.

>5. In general you care only about one product, no interface problems,
>no external utilities needed.

>6. The language is easy, very powerful, object oriented and visual.

Same with PB.

Also, w/ VFP classing & subclassing is powerful.


Benefits of PB,

1.Ability to access arguments, properties from ddlbs to paste in code snippets.
2.Datawindow object knocks the socks off of VFPs grid.
...