Spoke too soon. After a reboot, I had only IE and Homesite open, making changes to PHP code and running the app, and it hit an access violation. So SQLyog ain't it. -Chris On 9/6/06, Christopher Watson <skygeex@xxxxxxxxx> wrote:
Thanks for the input, Jon. I'll get to the Apache and IIS restart suggestions soon. Meanwhile, I think I have a semi-repeatable recipe for getting the access violation to happen. As far as I can tell, everything is cool until I open up SQLyog and do some sort of database manipulation within it. Almost immediately after that, switching back to the browser and flying through the app a little more brings on the violation. So far, my testing is indicating to me that the violation does not occur without SQLyog having done some work in the database. -Chris
-- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
