Who
Should Not Use
ProMatrix
|
|
| We at ProMatrix and
the vast majority of developers who use ProMatrix think
that every VFP developer should use ProMatrix. However, if you fall into the categories described below, you may not need ProMatrix. |
- Time Isn't
Important: If saving time isn't important to you, ProMatrix isn't for you.
ProMatrix could save you months, if not
years, of development time, but you would rather not save time. After
all, your time isn't worth anything. Because your time isn't worth
anything, it makes sense to spend thousands of hours creating what
Visual ProMatrix can give you for a few hundred dollars.
|
- Reinventing the
Wheel: If you get your kicks by reinventing the wheel,
ProMatrix isn't for you. You are only satisfied if you design every
aspect of your applications and write every line of code. After all,
nobody could do it like you.
|
- Bugs Aren't
Important: You don't care if your applications have bugs.
ProMatrix has been tested by many users for many years, and ProMatrix
is virtually bug-free. However, you believe that if you can't find
all the bugs by yourself, the bugs aren't worth fixing.
|
- You Don't Like
Working with Others: ProMatrix has a user community that
supports each other. However, you don't want to be part of any community that
might give you some useful tips and techniques.
|
- You Don't Build
Professional Applications: You don't build applications
with sound referential integrity, data integrity, audit trails,
security, data-driven messages, an extended data dictionary, an error
handler, multi-user capability, etc. What's more if you needed any of
that professional "crap", you would just take the next five
years to design it and build it yourself.
|
- World's
Greatest Programmer: If you're one of the world's greatest
Visual FoxPro programmers, it would be embarrassing to let anyone know
that you use someone else's framework.
|
- Money Is No Object: Instead of spending
less than $200 for VPM Standard or a few hundred dollars more for VPM
Enterprise, you prefer to spend thousands (if not tens of thousands) of
dollars creating your own applications from scratch because money is no
object for you. You couldn't care less about saving thousands of dollars
when you develop applications.
|
|
If even one of the categories listed above does not apply to you, you
should used Visual ProMatrix. |
| Obviously, we wrote
this page with our tongue planted firmly in our cheek. Hopefully, you get the idea that we think every
Visual FoxPro developer should use Visual ProMatrix. |
A
Logical Regression
|
| We're really amused when we hear a VFP developer say that using a
commercial framework is too inflexible, confining and limiting. If one
follows that logic to its ultimate conclusion, one has to ask: "Why
are they using Visual FoxPro?" They should be developing their own
database management system using machine language or, perhaps, C++. Then,
they can truly say they did it on their own and have ultimate flexibility.
You see a framework is to Visual FoxPro what Visual FoxPro is to C. It's
simply the next generation in the hierarchy of application development
tools. |
Take
Advantage of the Blessing
|
| As we have said before, Visual FoxPro developers are blessed to have
several good frameworks available to them. The fact is that you should buy
all the good ones. Even if you only use a few ideas or a few snippets of
code from a framework, that alone is enough for the framework to pay for
itself. |
| |
