[AccessD] Developer Extensions

If you are not doing the install yourself or you have no idea
what is on the machine and neither does the customer.
Or the customer is not local to you, you might want to look
at purchasing SageKey scripts, it gets around a lot
of OS glitches that might occur like hooking to the correct
version of Access, if the machine has multiple versions or
you are also installing multiple 3'd party ActiveX controls.

http://www.sagekey.com

Since you are not giving the code to the customer, you
might make em  feel more secure if you escrow the code
This doesn't have to be fancy just store a version with a local
lawyer or notary.  Some goverment departments are
insisting on this.

Dan Waters wrote:

>Hi Julie,
>
>The Packaging Wizard will package what you tell it to package.  So, go ahead
>and make your app an .mde first, then do the packaging.
>
>And - good luck selling to many customers!
>
>Dan Waters
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Julie
>Reardon-Taylor
>Sent: Friday, July 14, 2006 7:31 AM
>To: accessd at databaseadvisors.com
>Subject: [AccessD] Developer Extensions
>
>Hi Everyone,
>
>I thought (incorrectly) that the packaging wizard actually took the 
>application and made an mde type of file, then packaged the application for 
>installation.
>
>I found out that it still uses an .mdb file.  If I make an mde and then 
>package the application, that is the way to go?
>
>I have several applications that I am writing once and selling multiple 
>times to customer, (finally), and do not want the code accessible.
>
>Is this the only way to go?
>
>
>
>Julie Reardon-Taylor
>PRO-SOFT OF NY, INC.
>44 Public Square Suite #5
>Watertown, NY 13601
>Phone: 315.785.0319
>Fax: 315.785.0323
>www.pro-soft.net
>NYS IT Services Contract CMT026A
>NYS Certified Woman-Owned Business
>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada