> Note too that this same app ran fine on this > exact same computer for several years - and > the trouble started when they company's IT > department upgraded the PC software in some > way.
This is pretty important information... > The good news is that its no my programming > bug causing this and we can blame it on Windows NT > or something but the client won't like that, and > what can be done. It depends on one's perspective. If you built an application to run only on Windows 3.11, and it refused to work on Windows Vista, is this a bug in Windows Vista or is it a limitation of your software? This isn't exactly the same situation, but it does point to the fact that all computers are different and have different hurdles to overcome. The proper way, I think, to deal with this would be to: 1) Figure out why it's not working! 2) Go from there. You already know this, so... If possible, you should start with the client's IT department. Ask them what they might have done that caused your application to break. If the application ran on the computer for years prior to this recent upgrade process, there should be some sort of vested interest between your company and theirs. I can't imagine that they wouldn't be willing to work with you on this, or work on it on their own time--depending, of course, on the importance of your application to their company. I know that's how it has worked at any company I've worked at. It could be something as simple as a Windows, antiviral or anti-spyware permissions problem... HTH _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
