Visual Studio Vs Powerbuilder

[Former Member]

ok guys,

I have to prepare for a session to a meeting where I have to convince developers to switch from Visual Studio to Powerbuider.

Can you give me 10 good reasons for the mission?

ty

GMY

[Former Member]

Here's 4 for a start:

1.  The DataWindow allows for automatic handling of optimistic concurrency.  That is, you can tell it to check for update conflicts with just updated columns, or for all columns in the result set without having to add any special logic.

2.  The DataWindow renders at runtime as two controls, a bitmap and an edit mask, regardless of how many rows/columns are retrieved, reducing the demand on graphic resources.

3.  The DataWindow, if handled correctly, can be backend database agnostic.  You can easily have one set of code that supports a number of different databases.

4.  The Rapid Application Development features of the DataWindow and the PowerBuilder IDE mean that developers can be much more productive using the tool than other more 3GLish IDEs.

[Former Member]

While I'm not all that familiar wity Visual Studio, I do think I have one large item to add to the list:

5. Performance; PowerBuilder executes significantly faster than identical applications written in Visual Studio.

[Former Member]

3a. And when you use the DW painter, you don't waste time looking up the exact column name spellings or details of SQL syntax. For instance, when you do a join, it lists the options in plain English so you don't have to worry about which side of the = gets the *. And did I mention it's mostly point and click?