I VERY much appreciate the feedback … it helps not to feel isolated with a 
virtually unsolvable issue which affects one’s credibility with clients.  It is 
somewhat strange that this does seem to implicate LC to some degree, though.  A 
version of my code which (probably) used whatever LC version was fairly current 
in 2013 (I should, but don’t, keep track of what version of LC I use for 
various releases of my applications) DOES NOT exhibit this issue on the very 
same installations which are experiencing the error.

I would have used LC v 9.1 to produce the standalone which is *VERY* 
occasionally exhibiting this issue.  So … apparently … sometime along the way, 
LC changes seem to have “promoted” the potential for this error.

I’ve told the customers that I cannot possible fix something which I cannot 
reproduce.  I’ve also insinuated that even if LC *does* discover and fix the 
underlying issue, that I *WILL NOT* re-issue a new version with the VAST 
majority of 5,000+ installations NOT experiencing a problem … citing the amount 
of regression testing which would be mandated as a part of such a revision.

Again, thanks for the responses… this group is ALWAYS awesome in its support 
and knowledge!

Douglas Ruisaard
           
    Trilogy Software
      (250) 573-3935



-----Original Message-----
From: use-livecode <use-livecode-boun...@lists.runrev.com> On Behalf Of Bob 
Sneidar via use-livecode
Sent: Thursday, August 18, 2022 8:28 AM
To: How to use LiveCode <use-livecode@lists.runrev.com>
Cc: Bob Sneidar <bobsnei...@iotecdigital.com>
Subject: Re: issue related to Print.PrintSupport.Source.dll

Not unheard of. Some years back we discovered that if the HP Universal Print 
Driver had been installed, Toshiba drivers would not work at all. We had to 
uninstall the HP Universal Driver and replace it with the model-specific 
driver. 

Bob S

> On Aug 17, 2022, at 16:27 , Mark Wieder via use-livecode 
> <use-livecode@lists.runrev.com> wrote:
> 
> On 8/17/22 15:02, J. Landman Gay via use-livecode wrote:
> 
>> We had one instance where the user didn't have a printer at all, but just 
>> deleting the Epson driver fixed it.
> 
> ¯\_(ツ)_/¯
> 
> -- 
> Mark Wieder
> ahsoftw...@gmail.com
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to