|
|
|
| |
Information |
|
|
| |
|
| |
|
|
|
| |
Free Trials |
|
|
| |
|
| |
|
|
|
| |
ProMatrix Store |
| |
|
| |
|
VPME Beta
Tester Favorite New Features |
|
 |
These
are a Few of My Favorite Things!
We asked the VPM Enterprise
Beta Testers to give us a list of the major new benefits of VPME and the
reasons that a VPM 6.0 user would want to move from VPM 6.0 to VPM
Enterprise. Here's what they told us in their own words. |
|
| Edhy
Rijo (ProMatrix MVP) said: |
| One of the things I like the
most is the new OOP rewrite in VPME. Besides all the benefits that OOP
brings to us, you eliminated a dozen individual programs that used to make VPM harder to maintain. One example is the main application program
(sPrefixFMAN.PRG). In all my applications I have specific main program
modifications to show a splash form, verify that the program is running,
verify License approval, etc. Before VPME I had to modify the main program
in all my new projects. Now I can just add those changes at the VPM class
level. That makes my life easier. This is just a small benefit that means
a lot to me since I am frequently creating new projects |
| Hank
Fay |
| By far the greatest benefit is
the ability to do validation on the client or on the server. This allows
the use of fast/free c/s like mysql, on the one hand, where validation
must be done on the client; and the use of any other full-featured c/s
like SQL7 etc. for greater speed of processing on the backend validation
where required.
Second would be the movement toward OOPing
the framework in general. This will allow much greater flexibility in
modifying the framework to meet our needs.
Third would be moving the business rules
out of the forms. |
| John
Gunvaldson (ProMatrix MVP) said: |
| Visual ProMatrix Enterprise, ie:
"VPME" _Directly_ and _Effectively_ competes with several
features in the "Powerbuilder" environment (VPME 7, 8 and 9
advertised by Joe <g> will pick up and move beyond the rest of those
features, yes?).
Powerbuilder used to be the Client Server
Application Framework / Language of choice for certain Database
Applications (Sybase backend in particular). VPME opens this playing field
to a Microsoft Solution with Visual FoxPro / xBase and a host of
experienced VPM developers - in a "Big Way"!
Way Good for business!
In particular, VPME would have equally
Great performance, and excel with a Sybase SQL Server backend - just as it
does with Microsoft SQL Server database... VPME provides "In the
Box" support for these heterogeneous database environments!
## Powerbuilder Features VPME directly
competes with ##
- COM components for deployment to
Microsoft Transaction Server (MTS).
- Control over component transactions.
- Support of ResultSet and ADOResult types
for returning database result sets from components.
- Live Editing for testing components.
- Start Wizard facilitates creation of
workspaces, projects and files.
- Object Centric Development.
- New Wizards to simplify the creation of
applications and components using a new and simplified development
model. [We've been doing this with ProMatrix for how long now? - since
1995 for me <g>... ]
- Recently used Objects, Applications, or
Connection List .
- Non-modal, multi-pane environment based
on View technology.
- Personalized Keyboard Shortcuts.
List goes on and on, but one gets the idea.
"VPME" is ready to compete at a much higher level and offer
Sybase users a better "Microsoft Windows Standard" method of
High Quality RAD Application development.
Wish I could have seen VPME when the navy
picked Powerbuilder and Sybase. No question the Navy would have considered
a Microsoft Developed Solution - over Sybase. |
| Steve
Buttress (ProMatrix MVP) said: |
| Other than the obvious, remote
view services and OOPifying (is that a word <g>) the framework, the
changes I welcome the most are the technical improvements.
Some the technical improvement I
particularly like are:
- Restoring the text navigation keys
( Ctrl+Home, Ctrl+End, etc.).
- Leaving F2RefTable open.
- Improved PK generator.
- Elimination of global variables and what
that means for Error handling.
- Related forms functionality with RI on
Views.
- Moving PRG functions to oApp methods
(part of the OOP changes, but sufficiently important warrant specific
recognition).
- Use of Scatter Name for system records
like the DD, oSec, etc - a REALLY NICE FEATURE - as it makes
accessing properties stored in DD2 easy for VPM and the Developer
to use.
- Support for Candidate Keys.
|
|
