You just didn't know the right tricks. WHen I used it, we had genuine IBM PC's for network stations with a Novell 68B file server (115K twisted pair cabling! SLower than my ISDN link). The shop was a machine shop where we had to track every step of every process (we made aircraft engine part - the audit trail is amazing. Theoretically you could trace a failed part to the very hour and worker who machined it and which machine he used). There was a report I needed to produce that did a breakdown on all this activity - some 10K records per day. Version 1, before I learned the tricks, got started Friday afternoon after the server backup finished and JUST started printing to the laser printer Monday morning. It took longer to select the records than for a LaserJet II to print the 150 pages of the report. Then I learned the trick - you could read the index values directly and use those to locate the desired records. I learned that one at a user's group I belonged to. The second version of my report now took 15 minutes to do the query - the very same result set from the very same data source on the very same hardware that previously took 2 1/2 days!
Not Foxpro speed, but just about as fast as most of the other DBMS products at the time. On some decent hardware it was even nicer, but the fastest machine I ever saw an ARev app run was a 386 level system.

>I did some ARev too. While it was powerful, but was sooooooo slllllloooooowwwwwww. We had a personnel system that was developed by our payroll processing company.
>
>