I have been developing in Access for many years. From 2000 - 2010 I am having difficulties figuring out a deployment strategy. This new publish or package options is confusing both have advantages and disadvantages. I have started a thread on another site and have hundreds of posts from people with questions and answers. What do you think about putting a topic on here called "Packaging and Deployment".

My problem is I need to create a process to deploy apps through the network. Our network guys want to be able to restore computers and deploy applications.
I have for years deployed my application A2003 apps mamually. Digitial signing and placeing them in the userd App Data dir. We have a script that the network guys used to push out revisions. They now don't want to do thia anymore.
I was able to convience my manager the upgrade everyone to Office A2007-A2010 because it allowed earier deployment of the FE, could be made readonly accdr files.... I layed it on thick and they bought it spending Thousands's of dollars. How I am faced with a problem because I still cannot deploy signed packages as I said we would be able to.
I am not the only one with this problem. I have seen many posts on this Froum and others most say don't waste your time, use a outside deployment packager and deploy mdb's witch you can still sign at the development level.