"Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment" [1]
Plz check the enumeration of problems in "Problems using server-side Automation of Office" section of [1]
Had not I answered it [2a] in you previous question [2] that in order to deploy one should have managed something to deploy first, i.e. first manage to develop on developing machine targeting the same environment as target machine?
If you cannot manage to do it with SQL Express, you certainly wpuld not manage it with MS Access. It is more complocated and involved.
Update:
I still insist on my answers.
Deployment is not magic nor fortune teller, it will not correct your configuration errors or guess what you did not bother to formulate or even wish about. You confuse deployment with the necessity of configuration or even setups as well a knowing them
You cannot deploy without configuring (or knowing) production and developing environments and properly formulating your objective (and question) accordingly.
Just because you do not know what you want, what you can and how does not mean that you cannot believe your eyes.
Cited:
CITED:
[1]
Considerations for server-side Automation of Office
http://support.microsoft.com/kb/257757
[2]
Why do “I get Failed to generate a user instance of SQL Server” with .NET 4 and not .NET 2 ?
http://stackoverflow.com/questions/3901833/why-do-i-get-failed-to-generate-a-user-instance-of-sql-server-with-net-4-and-n
[2a]
My answer to your question [2]
http://stackoverflow.com/questions/3901833/why-do-i-get-failed-to-generate-a-user-instance-of-sql-server-with-net-4-and-n/3902890#3902890