[AccessD] Runtime Driver

You have my sympathy.  The MS-provided wizard is marginal at best and
well worth its price--free.

Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stephen R.
Zayko
Sent: Tuesday, April 08, 2003 8:22 AM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Runtime Driver


I was just going to use the VBA Package and Deployment wizard that comes
with the Office 2000 Developer CD.  I have had it for 3 years now and
never had a need for it until now.

-Z

Stephen R. Zayko
 
SECOR International Inc.
2321 Club meridian Drive Ste. E
Okemos MI, 48864
 
517 349 9499 ph
517 349 6863 fx
 
szayko at secor.com <mailto:szayko at secor.com> 
www.secorlansing.com <http://www.secorlansing.com> 
 


> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte 
> Foust
> Sent: Tuesday, April 08, 2003 11:50 AM
> To: accessd at databaseadvisors.com
> Subject: RE: [AccessD] Runtime Driver
> 
> 
> What are you using to build the installer?  One of the script driven 
> installers, like Wise or InstallShield should allow you to do this.
> 
> Charlotte Foust
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stephen R. 
> Zayko
> Sent: Tuesday, April 08, 2003 7:41 AM
> To: AccessD at databaseadvisors.com
> Subject: [AccessD] Runtime Driver
> 
> 
> Group:
> 
> Is it possible to include the drivers needed for a runtime
> solution?  I
> have an A2K database which I would like to package as a 
> runtime.  It is
> an A2K FE with a MySQL BE accessed via ODBC through the web.  Trouble
> with the distribution is that people must install the MySQL 
> ODBC driver,
> and then create/link to the machine data source of the MySQL 
> database (I
> think I said that right).  
> 
> What I would like to do is this...
> 
> Create the runtime with the drivers and the source database info. Then

> when a user unpacks/installs the runtime,
> 	A: The MYSQL driver installs on that machine and
> 	B: The ODBC data source is created with all the needed info.
> 
> A looks pretty simple to do.  You just include that in the files to be

> included during the packaging of the app. B however, I am not too sure

> about.  Can I do this through code?  Has anyone else done this before?
> 
> thanks in advance.
> 
> -Z
> 
> Stephen R. Zayko
>  
> SECOR International Inc.
> 2321 Club meridian Drive Ste. E
> Okemos MI, 48864
>  
> 517 349 9499 ph
> 517 349 6863 fx
>  
> szayko at secor.com <mailto:szayko at secor.com>
> www.secorlansing.com <http://www.secorlansing.com> 
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com