There are a few articles in the MSDN KB that talk about how MFC calls AfxDaoTerm from the ExitInstance of CWinApp, and how this can create problems with DAO objects declared at global scope or in DLLs etc. Seaching for afxdaoTerm will bring up about 4 or 5 articles that are almost-but-not-quite your scenario. Calling AfxDaoTerm directly is indeed one of the solutions mentioned. HTH

Hi, The good news: There is a comprehensive security setup document suite inside the help files of Access. It is relatively easy to read. The bad news (for me): I could not get it to work reliably and usually couldn't get the options that I wanted. I gave up eventually. My advice: download the miniSQL server version from vstudio in MSDN. It's called MSDE. Here's a link to a Jet vs MSDE debate: http://msdn.microsoft.com/library/default.asp?URL=/library/backgrnd/html/msdeforvs.htm&RLD=462. Here's a link to the MSDE itself: http://msdn.microsoft.com/library/default.asp?URL=/library/backgrnd/html/msdeforvs.htm Hope this helps. Kind regards, Al. VBer who wants to go back to, but will have to learn again, C++. I'll carry on using VB for the front-end; so when I get proficient at C++/STL can I jump straight to ATL and avoid the MFC?

try looking at OnCtlCOlor Function AFter InitDialog it would call this function which does the painting of all dialog controls and the dialog RObin