Add me to the SLOOOOW list. FMP6/WebCompanion/CDML 500 records, search, sort, calculate = 13 seconds to completion (finalized in graphic applet).

Just converted the whole mess to FMP7 SA, using Lasso 8 and inline commands, 500 records, search, sort, calculate = 53 seconds to completion (finalized in graphic applet). This is unacceptable, disgusting and pathetic.

This is a web-enabled example. I have spent a good 4 days hyper-customizing and streamlining this database solution - all energized by my faith in FMP - but it is waning - very, very fast. The XML Link to Lasso is sludgey chunky. Slow and plodding. Someone needs to get their act together. A warning to newbies, don't ask FMP to sort ANYTHING either!

I can search, sort, and calculate over 60k records over lasso, getting about 11k back in under 20 seconds, perhaps its not lasso or FMSA, triple check your calculations, make sure you don't have something messed up.

Found out what was wrong. (It's always me - isn't it) Eliminating my relations (in portals) cleared up all the delay. Then I slowly enabled the relations on test records I created manually. There was no delays! Then I discovered that FMPSA7 was choking (bottlenecked) on records in my relationships that had binary nulls in them. Apparently my mainframe feed supplies data to me that FMP6 never had a problem with. BUT FMP7 went nuts on this. Missing data on my mainframe database is filled with binary nulls that I COULD NOT SEE. After I remove them (with a filter I wrote on the mainframe) LASSO and FMP7SA really runs FAST!!! So mea culpa, mea culpa, mea culpa, (latin), the Lasso people were confused on this and so was I.

Glad its working for you, lasso is working great for me too.