Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Upgrade Issues
Message
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Divers
Thread ID:
00787121
Message ID:
00787134
Vues:
29
>Hi All;
>
>Today I compiled my vfp5 application in vfp8. Most of the errors where legit and are already taken care of except for the following issues:
>
>1) DOEVENT().
>I have a DOEVENT() in many forms that use some external ActiveX component. Mainly to prevent "racing" conditions, and trying to sync vfp application with the ActiveX process. Now under vfp8, I have to use DOEVENT(.T.) (to force it), and there is also that serious WARNING in vfp8 Help for using it. I need to run both vfp5 and vfp8 runtimes.
>Question is: What is the best way to handle the change in DOEVENT() functionality to work in both versions ? Should I use #IF statements?


DOEVENT is a command not a function and using it with parenthesis will generaten an error in VFP8. To make it work the same way as in VFP6 and earlier you would use FORCE option DOEVENTS FORCE. I would suggest that you try first w/o that option and see if it works.

>2) In vfp8, my main FORM is displayed in "Transparent" mode !
>The frame is displayed, but the instead of the form, foxpro's background screen is shown. However, all the buttons on the form work!.
>Then, the first Refresh(), after the form is active, draws the form. I had a thisForm.screenlock set to .T. and then back to .F., which I took out, but it still did'nt help. What could be causing that ?


What your custom property screenlock does? Check forms LockScreen property.

>3) SET SYSMENU TO DEFAULT
>causes "Fatal Exception Error" when releasing a form (in the Exit button Click() event). The "Sending Error Report to Microsoft" prompt never stops!, and I have to go to Windows Task Manager, eveytime, in order to Terminate vfp8. I don't know whether this is an error that should be reported to Microsoft.
>Is this a conformed error ?


I would try to delete foxuser.dbf. If that doesn't help, you may try to use PUSH MENU/POP MENU to save and restore menus.

>(Was surprized to see the file: vfp8err.log created in this case, which helped me find out which line was causing the Fatal Exception error. I love this feature!. I Hope it is also available in Runtime.)


>Thank you in advance.
>Cyrus
--sb--
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform