[AccessD] Slightly OT: Installation protocol

John W. Colby jcolby at ColbyConsulting.com
Tue Mar 18 09:17:00 CST 2003


Ranting and raving?

in fact something strange is happening with this digital sig thing I'm
trying to use.  I reply to a message one time and it appears to be locked,
can't be read.  Another reply(this test you replied to) is not locked.  

the technology is not ready for prime time methinks.

John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com]On Behalf Of William Hindman
Sent: Tuesday, March 18, 2003 10:07 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Slightly OT: Installation protocol


JC

...I know! ...I know! ...you're testing our patience! :)

...what happens when we fail? :)

William Hindman
"The tree of liberty only grows when watered by the blood of tyrants.
"Bertrand Barère de Vieuzac--a Frenchman


----- Original Message -----
From: "John W. Colby" <jcolby at ColbyConsulting.com>
To: <accessd at databaseadvisors.com>
Sent: Tuesday, March 18, 2003 9:34 AM
Subject: RE: [AccessD] Slightly OT: Installation protocol


> test again
>
> John W. Colby
> Colby Consulting
> www.ColbyConsulting.com
>
> -----Original Message-----
> From: accessd-admin at databaseadvisors.com
> [mailto:accessd-admin at databaseadvisors.com]On Behalf Of Bryan Carbonnell
> Sent: Tuesday, March 18, 2003 9:00 AM
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] Slightly OT: Installation protocol
>
>
> Here's what I do.
>
> When I build a setup for a VB App, I give the user the ability to NOT
> install the VB Runtimes (which oleaut32.dll is one) if they so choose. I
do
> have it set to install by default though.
>
> I only install the runtimes if an older version is on the system, but
before
> I do that, I back them up. I don't give the user a choice, they get backed
> up. Period.
>
> When the app gets uninstalled, if there are files in the backup directory,
> then I ask if they want to restore the DLLs to the pre install state.
>
> If they do, great, they get restored, if not, the backups get deleted.
>
> There really isn't anything that can be done in your situation. As others
> have said, welcome to DLL Hell.
>
> Bryan Carbonnell
> bryan_carbonnell at cbc.ca
>
> >>> andy at minstersystems.co.uk 18-Mar-03 7:14:17 AM >>>
> I'd like to know from you who install your VB apps on other
people'smachines
> whether it's normal practice to overwrite system dll's that areolder than
> the one you're sending out, without asking or telling? A userhere
installed
> a demo which installed a version of oleaut32.dll. Theirversion was newer
but
> it stll messed up my Access app, specifically where ittalked to Outlook.
Do
> I have a grouse?
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
>
> ----------------------------------------------------
> Is email taking over your day?  Manage your time with eMailBoss.
> Try it free!  http://www.eMailBoss.com
>


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



----------------------------------------------------
Is email taking over your day?  Manage your time with eMailBoss.  
Try it free!  http://www.eMailBoss.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 3200 bytes
Desc: not available
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030318/650b339b/attachment-0001.bin>


More information about the AccessD mailing list