I have an access program with extensive vba in it. When I open the program through the back door bypassing all the startups and run the process it works fine. However, when I open it regularly and the process autoruns I craps out with a message saying it cannot find function "blah blah". Now I know the function is in there and spelled correctly. This process is started through the main startup form. Is it possible that the when the form launches and begins the process that the modules have not been loaded into memory yet? Everything else runs correctly and that's the only call I have to a module in the startup form. Is there a way to force load the module from the form before starting the process?