[AccessD] Independent Developers Question

I think there are several reasons to choose early or late binding, it al depends on your software and the way you work. But that is another discussion. I found a bullet proof (it has not proven me wrong until now) method i used the past 8 years. I always use early binding and am making sure all referenced dll, objects are also installed in the program folder. I never have reference problems!!! I have a access mde database which i have distributed to about 700 different customers of my with 2 yearly updates. in 99% of the cases there are no problems.

The backside of this is that i have local for example outlook dll which are not applied with security packs etc. I state this in the manual and give my clients advice how to coop with this.

Regards, marcel


-----Original message-----
From: MartyConnelly martyconnelly at shaw.ca
Date: Mon, 5 Dec 2005 23:08:00 -0800
To: Access Developers discussion and problem solving
accessd at databaseadvisors.com
Subject: Re: [AccessD] Independent Developers Question

> Just remember there is a limit to testing, sometimes it is better to 
> keep track of known failure points
> 
> For example an Access program that calls Outlook
> A wise programmer might use late binding via
> Set olApp = CreateObject("Outlook.Application")
> This way I avoid any reference version problems with Outlook.
> Good move developer.
> 
> But OH NO, Symantec and other AntiVirus programs
> have recently taken to add script blocking on the above statement,
> to avoid address book theft in Outlook. And Access throws a 429 error
> 
> Now do you go back to writing everything with early binding
> or just have a good cry.
> 
> 
> Reuben Cummings wrote:
> 
> >I have a total of 8 laptops and 4 PC's (maybe more) allrunning different
> >OS's. They are not all here, but I can get them if needed (my nieces and
> >nephews use the laptops a lot for school). I never get rid of computers - I
> >loan them out with the understanding that I may need them back occasionally.
> >
> >However, after making a point to thoroughly test on different platforms A
> >LOT I have stopped doing so because, again, I have never found a conflict on
> >ANY OS or any configuration. The only current problem is that I cannot
> >create an installation using PDW on MY current laptop as it creates an
> >installation that returns an error that upon running says something like
> >"the files on the computer are out of date..." or "cannot be updated..."
> >or something. I simply use a PC that also sits on my desk to create an
> >install.
> >
> >The PDW is A2000.I still development in A2000.
> >
> >Reuben Cummings
> >GFC, LLC
> >812.523.1017
> >
> >
> > 
> >
> >>-----Original Message-----
> >>From: accessd-bounces at databaseadvisors.com
> >>[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Joe Hecht
> >>Sent: Monday, December 05, 2005 12:23 PM
> >>To: 'Access Developers discussion and problem solving'
> >>Subject: Re: [AccessD] Independent Developers Question
> >>
> >>
> >>Ruben,
> >>
> >>
> >>[Joe Hecht] You said
> >>I develop and test everything myself. Maybe I'm really good
> >>or really lucky, but I have yet to have any major problems
> >>go out the door.
> >>[Joe Hecht]
> >>Do you have a spare machine? How doyou do your testing?
> >>
> >>Is the PDW in A2K3 or is it VSTO?
> >>
> >>Thanks
> >>
> >>Joe Hecht
> >>jmhecht at earthlink.net
> >>
> >>--
> >>AccessD mailing list
> >>AccessD at databaseadvisors.com
> >>http://databaseadvisors.com/mailman/listinfo/accessd
> >>Website: http://www.databaseadvisors.com
> >>
> >> 
> >>
> >
> >
> >
> >
> > 
> >
> 
> -- 
> Marty Connelly
> Victoria, B.C.
> Canada
> 
> 
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com


_______________________________________________________________________
E: oost at e-business@start.com
F: +31-84-758-0746

Dit e-mailbericht is uitsluitend bestemd voor de geadresseerde(n). Indien de e-mail bij vergissing bij u terecht is gekomen, wilt u ons dan direct bellen? Wij verzoeken u in dit geval de e-mail te vernietigen, de inhoud ervan niet te gebruiken en niet onder derden te verspreiden, omdat het bericht vertrouwelijke informatie kan bevatten, beschermd door een beroepsgeheim. Wij danken u vriendelijk voor uw medewerking.