Hi Tom As we are deprived of daylight this time of year on the upside I spent the last 3 hours cutting my problem database to the bones and sent it off to Razzak & Co.
>Can happen first time accessing that form straight after starting >an R:BASE session or after being in for some time, so it does not >appear to be related to consumed memory not being released. That's what I thought a while ago so I became a QUIT TO freak. Whilst this improved stability no end the quick draw merchants can still crash R:Base by clicking too quick. I now have a fool proof test: Call the form from a choose command (CHOOSE vchoose ............;EDIT USING formename WHERE columnname = .vchoose) placing a problem button underneath the same mouse position as was used on CHOOSE. A double click will first fire the CHOOSE then the EEP on the forms button, no need to move the mouse. Every time a winner even on a 1GHz machine. My test button on the form runs another CHOOSE. Both the form and the superimposed CHOOSE look fine. The next click causes the crash. Ian ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
