Do not move Access to the startup folder.
Create an Icon that runs your application. If necessary, edit the icon with the command line options you might need for it. Access Help will show you what you need to know about command line options. Then create a shortcut to the desired MDB file. Then copy that shortcut (CTRL/C type of copy or right-click and select "Copy" - that sort of thing). Then right-click on the start button and left-click on EXPLORE ALL USERS. Find the "ALL USERS" tree under Documents and Settings, where you see "Start Menu" >> "Programs" >> "Startup" as a path to a folder with other icons that also are started for all users. Paste the shortcut you copied earlier into the startup folder for "all users."
ALTERNATIVE: If this is selective and multiple users have access to the same computer, find that path for each individual user to whom this applies and paste that shortcut icon in each per-user startup folder.
Be warned that this has the potential to annoy the living crap out of your user base. Particularly if you are using a shared backend or a shared MDB file that you have secured. Because in that case, you might end up forcing a user to log in to the machine a second time. (Once for windows; once for your application.)
Your question is simple enough. Startup is easy. But if you have started the database in the background, to drop it to the sys tray says it will never exit. I would be EXTREMELY wary of this as it implies you ALSO have to start an orderly shutdown of Access if you want to reboot the machine, which will be an issue to consider. And if you DON'T do the orderly shutdown, the odds greatly favor that you will quickly corrupt the database in question.
FURTHER, Access is capable of REJECTING a QUIT command if it happens to be doing something at the time. Which means your user will get the dreaded "This application is not responding ...." dialog that has the button on it that says "End Now" - and bang/zoom, there goes any chance of maintaining file integrity because you will be doing a disorderly close of the application. A disorderly close has a virtual CERTAINTY of corrupting your application files within a week unless you are one of the damndest prograrmmers we've ever seen around here.
So we've told you how to screw yourself really well. But I would be remiss in my obligation if I didn't also warn you that a screw job is imminent.
