|
Want to “go GUI” without
going broke? And still retain the Legacy Code and Database you have so much
invested in? You don't have to leave PICK or RPL to "go GUI"!
Did you know
that programmers write
AccuTerm GUI code in 100%
MultiValue Basic, but the screens run in Visual Basic and C? We can "put a GUI face on an old
friend" faster and at less cost than you would think possible. We can upgrade
just one screen, several, or your entire software suite. So if you have PICK or
RPL programmers on staff, they won't be left pounding the pavement.
Making the case for AccuTerm
GUI
 |
No large
up-front investment: MvCaTs can
"reengineer" one screen at a time and attach it to your existing character-based
menu. This method makes it MUCH easier on your budget. And we can
usually produce one or more screens per week so there won't be any "jet lag"
while awaiting "the big reveal".
|
 |
No data
conversion required: There
is no need to "normalize" your powerful three-tiered data files to accommodate a
conversion to Windows. AccuTerm GUI easily deals with your multivalued
data. This fact alone will save you a great deal of cash.
|
 |
No costly
retraining needed:
The learning curve for AccuTerm GUI is virtually nil. Any User who has
worked with a Windows application will be able to navigate an AccuTerm GUI
screen with ease. And MvCaTs Version Control enables User Preference.
Individual users can decide whether to run the OSV (Original Screen Version), the
reengineered CBI (Character Based Interface) version, or the GUI (Graphical User
Interface) version based on a control flag. Both
the CBI and GUI versions will have a layout very similar to the OSV.
A simple generic Application Name will be attached to
the character-based menu. When a user chooses that menu selection, Version
Control checks User Preference then runs the preferred screen. And with
Version Control, we can reverse the rollout of a new screen version in a matter of
seconds if something unforeseen occurs that would require the new version to revert to development.
|
 |
Get the best of
both worlds:
Programmers write AccuTerm GUI code in 100% MultiValue Basic, but the screens
run in Visual Basic and C. They have the complete "look and feel" of
Windows applications. MvCaTs takes existing character-based screen code
and "reengineers" it to share most of the code with the GUI side by parsing into
"GUI-friendly" subroutines for validation, data retrieval, file updating, etc.
These subs are also called by the event-driven GUI side to "do just one thing"
based on the object the user clicked. Changes to source code in the CBI subs are
automatically reflected on the GUI side, reducing maintenance cost and time.
And changes to the online help for CBI prompts are automatically reflected in
the GUI help hint balloons. How cool is that!
|
 |
Keep data entry
staff happy: Personnel who are accustomed to rapid data entry
via "green screen" tend to be resistant to the thought of a GUI
upgrade. So they should be quite pleased to learn that after MvCaTs
reengineers a screen, they can choose to run the CBI version instead of GUI if
desired. The CBI version, which shares its subroutines with GUI, will look
the same as the OSV (but will have a screen border to act as a "container").
It will perform the same and use the same commands as the OSV. But as an
added bonus, we can attach our Ticker Tape Text Editor to any non-GUI prompt.
|
 |
Get two for the
price of one: Our
CBI & GUI entry screens are written to include an INQUIRY flag so that one
screen can handle both Maintenance and Inquiry. Simply by passing a
special flag from a menu and placing a few "hooks" in the code, a Maintenance
screen can do "double duty" as an Inquiry screen. Then both stay
"in sync". This feature alone can
add up to significant savings, not only during initial development but also later, when
upgrades are requested.
|
 |
Screen Print capability:
Where applicable, we automatically
include a Screen Print command button on GUI screens & menus to provide a
convenient "snapshot". The OSV and CBI versions already have this
capability by clicking the "Print screen" icon in the AccuTerm window toolbar.
But when a GUI screen is run, the AccuTerm window itself is minimized so the
"Print screen" icon is not available during a GUI session. We thought it
would be nice to have this feature on the GUI side as well. As an added
bonus, this feature allows the user to select a printer rather than
automatically "dumping" to the user's default printer.
|
 |
Web Browser
Secure Access:
AccuTerm's Internet Edition provides secure access to your character-based
applications by clicking a link on the web browser. So if you have been
looking for a way to let your customers place their own orders online, look no
further.
Click here to learn more.
|
 |
Facelift -vs-
Funeral:
Over the years, we've
all heard the now well-documented horror stories of companies such as PG&E, GM,
Ford Motor Credit, Reynolds & Reynolds, and recently, the 23 store jewelry
chain Shane Co., who tried, at great cost and often unsuccessfully, to leave
PICK in order to "go GUI". But why throw out the baby with the bath water when
we can breathe new life into your old code? Then you can retain both the Legacy
code and database you already have so much invested in and that have run your business
reliably for so many years. Perhaps all you need is a
system upgrade to make you fall in love
with PICK or RPL all over again. If so, we can help you find the right system to
suit your needs and budget.
|
Now you know that you really can "go
GUI" without going broke.
But seeing is believing, so
we hope you will
Click here to request a FREE AccuTerm GUI demo. You will need
the most current version of AccuTerm installed on your PC. You can
get a
30-day free evaluation or a free upgrade by clicking here. Then via free Skype VOIP, our CEO will help you link up with our TigerLogic/D3 demo system by remote access for a free hands-on demo designed to erase every
misconception you have about AccuTerm GUI. We believe it's one of the best
kept secrets in the MultiValue world. And we're working hard to change
that.
|