jwcolby
jwcolby at colbyconsulting.com
Sat Jul 11 11:17:04 CDT 2009
Rocky, > What is the path to the Add-In folder? Well... It is AppData\Roaming\Microsoft\Addins However that is under jwcolby. What that translates to in the real world I haven't a clue. John W. Colby www.ColbyConsulting.com rockysmolin at bchacc.com wrote: > JC: > > I have Wise/Sagekey and, while not very expert in Wise, a simple install > should be a snap with the Wise template I have that does a simple install > and doesn't include the Access run time. > > I'm away at the moment but will take a look when I'm back in the office - > maybe send you a sample with an install of just a dummy text file or > something to see how it runs. The template gives a default folder for the > install, and allows you browse to a different folder if desired. Also has a > license agreement form as part of the process. > > What is the path to the Add-In folder? > > Rocky > > > Original Message: > ----------------- > From: jwcolby jwcolby at colbyconsulting.com > Date: Sat, 11 Jul 2009 10:56:11 -0400 > To: accessd at databaseadvisors.com > Subject: [AccessD] Help building EatBloat installer > > > Max has generously donated his EatBloat tool to Database Advisors. Dan > Waters and myself are both > rebuilding Eatbloat, but in different directions. I am working on an > Add-in which will be available > from the toolbar (Tools / Addins / Eatbloat) in any database you are > working on. Dan is working on > keeping EatBloat as a form which you import into a project to perform the > process. > > Because of the differences in the methods we are using, the end results > will be radically different, > yet perform basically the same functionality. We will end up with two > completely separate products, > and you, the developer, can choose which you would like to use. > > Dan's version will be used simply by placing eatbloat somewhere on your > disk, opening your > application, and importing a form from his Eatbloat container. > > My version OTOH will be installed somewhere on your hard disk and then you > will use AddIn manager to > add it in to your menu bar. While not required, it would be nice to have > an installer for my > version, where the installer places the addin in the Microsoft Addin > directory (yes there is such a > thing), whereupon it will be instantly visible from the Addin wizard. If > it is not placed there > then the user has to navigate to where they placed it. > > So... is anyone out there familiar with creating installers, and if so > volunteer to create an > installer for my addin? > > > TIA, >