What is the difference in SageKey and MS Access Deployment tools?

SageKey is more robust/complete and let's multiple access versions co-exist side by side happily.
The microsoft deployment wizard is problematic.  It works, but it has issues and it's not always easy to get answers when it doesn't.
JimD.
 

JDettman,
  Since I am new to MS Access Development, could you please explain in a little detail the following:

1. What is ment by "robust/complete"

2. What is ment by "and let's multiple access versions co-exist "

3. What is meant by: "microsoft deployment wizard is problematic"

4. In your professional opinion, is SageKey worth the $650.00 price?

Thanks,
CSSC1

Thanks

For the benefit of anyone who is reading this question to determine whether or not to use Sagekey (Like I was) I would like to highlight one, seemingly unadvertised, limitation of Sagekey.

Microsoft has made the the 32 bit and 64 bit versions of MS Access exclusive and not able to run side by side. Not even Sagekey can get around this one. So if the target computer has a conflicting version of MS Access you will have to remove it. See http://www.sagekey.com/support_forum.aspx?g=posts&t=1088

Thing is ... there is really no compelling reason whatsoever to be running 64bit Office (especially Access).

mx

<<Thing is ... there is really no compelling reason whatsoever to be running 64bit Office (especially Access).>>

+1

Outside of *very* large spreadsheets in Excel, or projects in project, nothing is different.

Jim.