Trace the problem to determine which object the "shut down" is occurring.
Rather than a corrupt DB, you may be experiencing a corrupt object. Once
found, create a new object and use that new object. Does the corrupt still
occur?
What code is being executed that the "shut down" is occuring? Are you using
Database, Recordset and/or QueryDef objects? If so, are you closing these
objects at the end of your procedure?
Yes, I do work for FMS, Inc.
--
Rob
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Problems with your database? Need to upgrade your application?
Contact the FMS Professional Solutions Group:
www.fmsinc.com/consulting
Need a Book Recommendation?
www.fmsinc.com/toplevel/books.htm
Need software tools for Access, VB or .NET?
http://www.fmsinc.com
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-