Hi, I figured this one out. It turned out that my container for holding the database connection ID wasn't valid in the exit script. With the correct ID the Windows memory fault notice went away.
Thanks Trevor and Paul for your replies -- they got me thinking. -- Harvey _______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
