Can I ever back this up. I am a VAR for a Sales/CRM software called SalesLogix. This program is written entirely in Borland Delphi.
I use VNC heavly to connect to clients and do customization work. I probably spend 8 to 10 hours a day in a VNC/PcAnyWhere session programming. In a given week, I will connect to a dozen different sites running VNC, so this is not just a random weird machine problem. Running the program from the console is no problems and there are never any problems. However, when connected remotely via AT&T VNC, TightVNC 1.2.1, or TightVNC 1.2.2 I frequently see the programs crash. The crashes are more likely if I am running more than one App(All Borland Delphi apps), and even more common if I minimize any of the apps. This is NOT a VNC problem. This problem is just as bad with PcAnyWhere. Other than remote access, these programs are very stable, so I think it has to be a piticular problem with Borland Delphi. If the VNC programmers could figure this problem out and fix it, many many people would switch to VNC because this is a problem for all Delphi apps I bet, but this is NOT their fault. Greg Breland On Tue, 2002-02-12 at 11:53, Jacob Hoover wrote: > Before I begin, I have searched the archives for Borland problems. However > they all lead back to > 16 bit Borland DLL's. I am having a problem with the vnc server and a 32 > bit Borland DLL. > > I have a problem with the VNC server (3.3.3r9) software and a Borland C++ > based application (prof.exe). --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
