If I can just add my two cents ...
You need to allocate Access runtime with your application. I recently heard about Stackoverflow that Microsoft's runtime for access is now free to download.
Here are some links ...
http://www.granite.ab.ca/access/developeredition2007faq.htm
http://blogs.msdn.com/clintcovington/archive/2007/01/30/the-runtime-and-developer-extensions-will-be-free.aspx
You can either distribute these runtimes with your application, or you can download their clients.
EDIT - NEVER FALSE. YOU SHOULD NOT BUY A LICENSE TO PROVIDE PROBLEMS. Of course, they are licensed, but the license is free. I leave a comment below for his historical interest.
I think, but I'm not sure, that in order to extend the access execution time with your application you will have to have a license. I know that you used this license with an MSDN subscription and with Visual Studio Tools for Office.
END FALSEHOOD
Once you have runtime, you can create runtime settings for BULLETPROOF Access applications using pre-configured installation scripts from SageKey.com .
Office developer tools come with some deployment options, but they are not bulletproof, and I will NEVER distribute a commercial application using these ... they just don't work. But the creak of Sagekey is absolutely ROCK. They work incredibly well.
All of this suggests that you want to distribute your application widely. If not (for example ... you just want to deploy your clients and you have full control over this), you can use the Microsoft download option mentioned above.
Last thing. Run-time access applications must be VERY reliable. You should do error handling and automatic table linking very well by the way, or you will spend all the time on the phone with your customers, and not sell / distribute the software.
Hope this helps.
Set
source share