Deployment Strategy

[darren via AccessMonster.com]

Hi

To date I have mainly built small one off databases and a few split network
solutions (mde FE & mdb BE). I would like to start learning how to take
create deployable for users beyond my network. I understand that ADE and VS
Tools have packaging wizards that deal to some extent with installation and
Access runtime.

I would appreciate your thoughts and guidance as to the design considerations
I should apply.

Perhaps most significantly I am wondering how at a later date I could provide
upgrades?

As always any help/guidance appreciated.

 

[darren via AccessMonster.com]

Perhaps, DISTRIBUTION was the term I was looking for. I've been trolling
through the threads and most seem to point out the problems not the solutions
to wanting to do this with a little cynicism from the Pro's to the wannabe's.
;o)

Anway from what I've gathered so far:

1) I need Visual Studio Tools for Office for Access Runtime and to create the
MSI file (checked ebay for alternative older tools but sadly lacking).
2) I then get a little confused with lots of talks about Installshield,
SageKey, Install2go .... but which and why?
3) Digital Signatures - required or not required?
4) Much talk of issues regarding Office and Access versions - does the above
software not solve these?
5) References to Office libraries (e.g. Word) causing problems?
6) I split my databases but is there anything to be gained in making the BE
an mde?
7) Aside from the Runtime limitations what other considerations should I give
to my design.

It's obviously a very big topic and I guess I could do with a little hand
holding as I walk the learning curve.

Without getting you to spoon feed me, what should be my first step and what
should I be looking to achieve?

As always, many thanks.

(P.S. Or should I just start building FE's in VS?!)