MartyConnelly
martyconnelly at shaw.ca
Wed Mar 17 12:42:16 CST 2004
You may have one other choice. I might be tempted to use SageKey MSI scripts rather than Wise, especially with the newer security on systems like WinXP SP2 (due out in summer) or Win 2003. It might make it easier to do a user install, rather than having to do an administrative one. Or even an install for running via Terminal Server. I am guessing here but a phone call to SageKey might resolve that one. SageKey MSI installs are available back to Access97, however with older OS systems you may have to upgrade the MSI installer to version 2.0??? The MSI install would perhaps save you the price of Wise. You could use the Package Wizard but will it get you around the problem of multiple Access installs? The BIG problem maybe that the Package Wizard requires a purchased security certificate to get around macro security. I am not sure the roll your own certificate method works, Sagekey Access 2003 MSI or Wise Scripts don't need this. But you may still need Wise with MSI, if you are installing complex OCX or dll files. This is real swings and merrygoround stuff. One advantage of buying Access 2003 VSTO is it includes VB.Net Pro, SQL Server 2000 Developer and the VS add-ins to create managed code projects for Word and Excel and three other Access developer add-ins. You can buy the VSTO upgrade if you have Access Developer 97 and up for $200 US http://msdn.microsoft.com/vstudio/howtobuy/officetools/ Rocky Smolin - Beach Access Software wrote: >Marty: > >A couple of weeks ago I was asking about deploying an Access product and >trying to decide whether to go with Wise/Sagekey A2K script with an A2K mde. >But I'd have to buy the A2K developer edition. as well as the Sagekey >script. > >Now it appears, IIUC, that I could buy Office 2003 and the Office Developer >Tools (I've got A97 Developer license so I could get the Tools upgrade >price, I think), and use the Developer Tools packaging wizard. > >>From the article it appears that the Packaging Wizard is pretty good. I >didn't detect any of the 'it really stinks' kind of review of earlier Access >packagers. > >Has you or anyone had any experience with it yet? Is it a reasonable >alternative? It probably would have a longer life than going with an A2K >solution. One requirement I see is that the target machine has to have W2K >or WXP but that shouldn't be too much of a problem as time goes on. > >Regards, > >Rocky Smolin >Beach Access Software >http://www.e-z-mrp.com > > >----- Original Message ----- >From: "MartyConnelly" <martyconnelly at shaw.ca> >To: "Access Developers discussion and problem solving" ><accessd at databaseadvisors.com> >Sent: Monday, March 15, 2004 11:30 AM >Subject: Re: [AccessD] Access 2003 Developer Edition? > > > > >>The Access 2003 runtime ships with any version of Office 2003 that has >>Access 2003, the license to redistribute solutions with the Access >>runtime is available exclusively through the Access Developer >>Extensions. The Access Developer Extensions include the Package Wizard >>and other developer-oriented tools. The Package Wizard creates a package >>based on an Access 2003 solution that users can install and uninstall >>with the Microsoft Windows Installer. You can only acquire the Access >>Developer Extensions by buying the "Visual Studio Tools for the >>Microsoft Office System". >>http://msdn.microsoft.com/vstudio/office >> >> >> Packaging Access 2003 Solutions Rick Dobson >> >> >> >> >http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsmart03/html/sa03j8.asp > > >>Michael Brösdorf wrote: >> >> >> >>>Hello, >>> >>>I noticed that there seems to no more Office 2003 Developers Edition. Is >>> >>> >it > > >>>still possible to create Run-Time applications with Access 2003? >>>` >>>Michael >>> >>> >>> >>> >>> >>-- >>Marty Connelly >>Victoria, B.C. >>Canada >> >> >> >>-- >>_______________________________________________ >>AccessD mailing list >>AccessD at databaseadvisors.com >>http://databaseadvisors.com/mailman/listinfo/accessd >>Website: http://www.databaseadvisors.com >> >> >> > > > -- Marty Connelly Victoria, B.C. Canada