Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Windows and Unattended mode
Message
De
07/12/2014 22:25:05
Neil Mc Donald
Cencom Systems P/L
The Sun, Australie
 
 
À
06/12/2014 18:56:04
Information générale
Forum:
Visual FoxPro
Catégorie:
Fonctions Windows API
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows 7
Network:
Windows 2008 Server
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01610803
Message ID:
01611966
Vues:
47
OK, Maybe just wrap your call to the network resource in a TRY ENDTRY and just restart windows from VFP when the network error occurs.

>Hi Neil,
>
>Sorry for replied so late. The whole program is actually using sys(2335,0) for unattended mode, BUT it is WINDOWS (7) that is coming with a messagebox! Is there any (api) function to tell windows that it should act for an unattended mode?
>
>
>>Hi,
>>Prevent the server from going into a modal state, use the SYS(2335,0) function early in the code, it causes Visual FoxPro to generate an error if any type of UI is attempted in the server code.
>>Trap error code 2031:"User-interface operation not allowed at this time" and do a restart or whatever you want to do in this case.
>>
>>>Hi all,
>>>
>>>I built a 'job processor' that runs in Unattended Server Mode [ sys(2335) ]. However, when a serious network error occurs it is WINDOWS that generates a message that requires a push on a button. Is there any procedure or (api-)function that can be used to prevent such a windows message?
>>>
>>>The job processor has been built to also handle any unexpected shutdown or even any spontaneous restart of the machine.
Regards N Mc Donald
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform