>That sounds strange. I am working on Active-X controls in VFP for auto parts. The PB/SyBase system is killer in speed. We purchased a port of it for use in VFP. My data return time is terrible as compared to their's.

Well, I would probably say a lot depends on the developers :) Our vfp apps kick-butt on the PB/Sybase apps here, I can tell you. One obvious problem is they have completely separate DB and GUI teams, doing the DB first, and then try to match the GUI to it late in the process. So, they end up with many forms needing data from many diverse tables, not an optimal situation. I work differently, doing GUI prototypes first, then DB design later.

Then I have seen some of the DB/code work done by PB/Sybase people. Disorganized, over-normalized DBs, SQL with twenty gazillion joins, thousands of stored procedures (some probably doing overlapping work), poor-indexing strategy, heavy reliance on ODBC...these are some of the problems, I'm sure, stuff you just know is going to slow things down - generally poor design work.

Sounds like your situation is the opposite, where the vfp is not optimally designed, but the PB/Sybase is...as I said to Dorris, Peoplesoft seems to have done a good job with performance, despite other problems, so I'm sure it's possible to build fast apps using either tool...