>>Hi,
>>
>>I know you must be tired of me, or my messages. Be patient; another 10 years and I will stop :)
>>
>>Good news is that I no longer get the errors (from this customer) of the lost connection to the SQL Server. I have already wrote about it.
>>
>>But I still see in the error log issues related to the application "reading" some libraries. Here is an example:
>>
>>A user clicks on an item of a toolbar, the program calls a method OpenAppForm which actually (as name suggests) opens a form. But the log file says that OpenAppForm had an error:
>>

>>Error reading file \\.......\appshare\libs\formfile.vcx
>>

>>The location \libs\ is where the library formfile.vcx reside at design time. And I understand that since the application cannot read this .vcx it refers to the design time name. This is fine.
>>
>>My question. Inside the OpenAppForm I can enclose the instantiating of the form in formfile.vcx (or any other) in Try/Catch. Then if the problem is determined, where should the code go? Simply informing the user that they have a problem? Creating a loop and attempting to instantiate the form 2-3 times? What else can I do with this Try/Catch?
>>
>>TIA
>
>After monitoring the error log and various other logs I created, I can now reduce the run-time errors almost to nothing. Basically, with the Try and Catch, I can prevent a run-time error and display why the program cannot open this or that form.
>My only question is, what kind of language to use when showing this "error message". For example,
>I can have a messagebox with the following text:
>

>"Cannot open Parts (or another window) Windows because your computer lost connection to the
>network/server.  Please close the "application" and open it again right away or in a minute"
>

>
>Does the above make sense (as far as the message)?

You forgot to ask each user every time to call the stakeholder and security guy hindering local install and praise them for unnecessary work they create...