Alec,
The error seems to conflict with your statement that the operation is non 
manual as it points to a problem with Menu popup's already being activated.

Do you mean that there is a user GUI but it is simply a case of "click button 
and go" or is it a gui-less app?

I would first of all remove any traces of foxuser.dbf if in fact you haven't 
disabled resources in the application itself and also get information as to the 
type of VM they are using i.e Vmware etc. from personal experience I have had 
some GUI issues with VMWare when the incorrect version of VMWareTools has been 
loaded as it contains the updated video drivers amongst its many facets. 
Whenever I encountered these problems, an uninstall followed by a re-install of 
VMwareTools solved the problem. 

I think you really need more info such as the resources allocated to the VM etc 
before you or anyone else can make a proper judgement.

Dave


-----Original Message-----
From: ProFox [mailto:[email protected]] On Behalf Of [email protected]
Sent: 19 September 2013 23:11
To: [email protected]
Subject: Help with: Fatal Error 182.. 

Hi Folks,

I am a semi long time VFP developer (since Fox 2.6), but vey new to this list.  
We have an application written in VFP 9 SP2 that is deployed at many customer 
sites.  The application functions as a back-office communications controller 
(via TCP/IP) accessing MS-SQL Server as the database.  Generally there is no 
user/operator interaction with it.  At most sites it runs 24x7 for months at a 
time without any issues.  In fact, most of the time when clients need to 
restart the controller it is because of an automatic MS
Windows update.   That said; at one site in particular they have received a
message that we have not seen before.  

The error is:  "Fatal Error 182 occurred while attempting to report error 182"

In doing a bit of research, this error seems to be one that appeared back in 
the VFP 7 but was reportedly fixed in subsequent releases of VFP.  

With respect to this one problem site; against our wishes and recommendations 
the client is running this application within a VM and I sort of suspect that 
the root of the error is perhaps associated with a resource issue (or lack 
thereof) created by the VM environment.  That is
obviously speculation on my part.   The local IT guy is insistent to the
contrary and firmly believes that the VM is not the problem.    

Anyway, has anyone seen this error before (especially in VFP 9) and if so, can 
you provide any ideas to its origin.

Thanks!

Alec Gagne
Crimestar Corporation
San Jose, California, USA




[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to