FMP6. Lasso 6. Mac 10.3. After creating unique 6 digit random numbers (no leading 0's) I am using Encrypt_MD5 in Lasso to loop through the records and record the encrypted version., which then gets put in the file the people log on to, the file with both versions is not web activated. The lasso loop gets a number, encrypts it, then passes it back to the encryption field. But FMP crashes, always unpredicatable. I have tried slowing lasso down with an extra loop, I've checked and re-checked everything, but go for 100 at a time and FMP always crashes. Can FileMaker take this kind of activity I am wondering?

Ah, that's interesting...!@# It only seems unpredictable... on consecutive attempts. After re-starting FileMaker it always crashes after looping through between 77 and 79 records. Is there some sort of limit on how many hits FMP can take without a breather? Me too I wonder. Is there some sort of buffer problem somewhere? Any ideas would be much appreciated.

Try increasing the "Preferences - Memory - Cache".

Good Luck.

Garry

p.s. Do you have the latest updates for FM6?

Thanks for that. Yes I thought that might help, but no. I've tried increasing the memory cache, decreasing the memory cache, flushing cache to disk, stopping and starting Web Companion from application preferences, from Sharing, stopping and starting Apache, and yet nothing substitutes for stopping and starting FileMaker. What is it I wonder that this does that re-sets the what-ever that causes it to crunch after 77 - 79 loops? I guess I can find a work around but I'm sure this is the same problem that has caused other crashes, such as probes by search engine spiders...

I'll look into the updates and post a reply if it helps.

Brilliant. I take back everything I have thought for the last few days, although I guess I was right to start with. I've updated the Web Companion and the Web Companion Enabler from the FileMaker site (hard to find but..) and now it's all peace on earth and good will again. It seems that the old Web Companion and Mac OS X must have had a few compatibility problems. Thanks Garry.