: All along, though, we have had performance problems. For the
: record, all P4W user machines are DEC 486/66, 16MB RAM, most
: have 2MB Video RAM, 256K cache. Screen resolution varies but
: most are 1024x768. All use run-time.
As PC magazine's tests have shown all along, use 640x480 at about 256 for
maximum WinVideo performance... But I personally use 1024x768... :-P
: So, what have we learned? For single user apps, especially
: where the main function is to report or inquire upon volumes of
: standing data, both development and runtime were very good.
: However, as soon as we got into transaction processing systems,
: and especially multi-user ones problems emerged. Transaction
: systems usually required some fiddling with the various
: arrive(), setfocus(), candepart() etc methods. As noted by Bryce,
: when you get into these, especially on multi-record objects,
: things slow down.
I've found that if I do some queries and those only retrieve a handful of
entries (less than a dozen or so), it's actually a lot faster to open a
tcursor and use locates to dump them to a temporary table. Of course, I
don't get all those nice relationships...
: With the higher resolution systems, screen refresh times were
: unacceptable to the users. Turning flicker-free off
: in one instance gave dramatic
: speed improvements, at the cost of some curious blinks one some
: screen objects, but mercifully not the complete form.
: All our applications originally had on their MAIN form, the
: NBNZ logo (you know, the Black Horse) plus some bitmapped text.
: Removing this object not only sped up the initial form load
: as you might expect, but all the other forms ran noticably
: faster. The bitmap was only 41K, so why this occurred
: is a mystery. Anyhow, we took them all off and get by with
: just a standard Text object.
Was that logo "zoomed" or stretched in any way? That will slow down
PDOXWIN quite a bit... Use the correct size to startwith, and leave it
: A big hassle was the size of P4W's footprint. Standard setup
: consumes about 25% system resources (measured by Winsock)
: compared with Excel 4's 17-25%. Runtime dropped this to 21%.
: However, with many user PC's already running over 60%, especially
: those in the Dealing room (some of which sustain over 90%!),
: the capacity was not there.
Agreed... I use the Paradox Desktop that comes with the book "What Every
Programmer should know about PDOXWIN" by Mike Prestwood, which launches
multiple sessions of PDOXWIN (one for itself). After two or three
sessions plus my other programs, AFTER DARK won't do any of the complex
stuff any more! :-/
: One application was a simple tableview showing the contents
: of a network file, which changed as the file contents changed
: as P4W should do and which we saw as a strength. Replacing just
: the form with a clone in Powerbuilder, still accessing the
: P4W database dropped the footprint from 21% to just 1%. This
: meant that the users could actually run it!
That's a good idea... I wonder how much GDI resource would a program
written in C/C++/WinPascal/VB and ODBC drivers would take?
[some things deleted]
: I should end by saying some positive things about P4W.
: One particular app stands out as a testament to the
: product. We support users in several NZ sites, and need
: details of who is where and what H/W they have. Our
: FLOORPLAN system initially shows a collection of buildings
: and you click on the building/floor you want. This
: displays a floorplan of desks with names etc. All
: objects are created dynamically from database
: of information about type and position.
: Right click on a desk, and person and H/W details appear
: and can be modified. Edit the details and the
: screen object changes to suit. Desks and/or H/W
: can be selected and dragged to a new position (or
: cut and pasted to a new floor - never got multi-form
: d&d working!).
: Selection criteria can be entered (such as show
: all desks with 386's. or who's on Ethernet), and
: all relevant objects change colour. Reports
: can be run on objects on the floor, or just those
: highlighted and so on. Anyway, we're proud of it, the
: admin user thinks it's neat and best of all it was
: both quick (about 5 days) and *FUN* to build. So regardless
: of the outcome of the current trial, we will keep
: and continue to use P4W for at least some apps.
Wow... That's a good one... Too bad Borland don't do a applications
contest like Corel with their art contests! :-)
|| (the rest of this .sig is under construction...) ||