I'm sorry to be writing this here, but I can't figure out why this is happening and hope that someone else has run into the issue.
We have a db that we converted from 4d 2004.5 to 11.5. When we run the db locally during development, the system will not quit properly because, after a time, it displays a dialog stating the A4D_Console process could not be quit. This is odd since the A4D_Console process is a local process and should, according to the docs,be aborted as soon as 4D begins the quit process (also local). We never had this issue with 2004 so I'm puzzled why this has started with 11.5 when that part of the system, as far as I can tell, has not changed from A4D 4.5 to 5.0. We followed the A4D docs in upgrading the structure and everything else works fine, ASFAIK Any idea what might be happening here? Thanks, Michael Check _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
