[AccessD] Developer Extensions

It depends on which Access version.  2002 and back required starting the
package wizard from the VBE (in the Add-Ins menu) so it had to be an MDB -
there is no VBE in an MDE.  
Since 2003 uses  VSTO, a completely separate product, you _can_ package
MDE's.

As for the older versions, although the documentation says you can't do it,
you can package your MDB, then create an MDE based on the MDB.  Create an
empty MDB with the same name as the original, and replace your orignal MDB
in the pkg with the empty (don't lose the source MDB of course). Add an
AutoExec in the empty MDB that opens the MDE then quits, so the wizard
generated shortcut will still work, and your MDE will be what the user runs.

Hth
Steve


-----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 8: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


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com