Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Was expected to be fixed but it's not
Message
 
 
À
03/03/2003 17:28:31
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00760584
Message ID:
00760870
Vues:
36
>In VFP 7, I reported to Microsoft VFP team twice a bug and a simulation on how to reproduce it. I thought it would have been fixed in VFP 8, but it's not. So, I'm still looking for a workaround on how to resolve this issue. When this is happening, it is really annoying and irritates me a lot.
>
>I have a transfer program that I have as a console monitor to upload EXEs to various Web servers in production. Those Web servers handle specific Visual FoxPro applications for specific clients. So, when time comes, we run the application from the Windows shortcut and click on the proper button to compile the specific project and upload it to the required server. This is not an EXE as I am using a BUILD command inside of the application.
>
>The situation is that after a while, randomly, it could happen on the first try, when trying to BUILD the application, Visual FoxPro generates an error. There is no reason for that error as the project is closed. So, when I have this, no matter how many times I try it, I have to close the application and restart it again. Then, this is somewhat cleanup memory of whatever and the next BUILD on the same application will work.
>
>So, I can work for hours with that console monitor. Then, suddently, without any reason, the BUILD no longer wants to work. This is internal to the application. Even if I close the other copy of Visual FoxPro I have, this is no effect. I really have to close the application in order to reset its memory.
>
>It's not about the number of times I build, not about the time the application has been running. It's just happening at any time when it starts to happen.
>
>My button has a call to something like this:
>
>
>BUILD EXE \MyMainDevDir\MyApplication\MyEXE.exe FROM \MyMainDevDir\MyApplication\MyProject
>
>
>So, at first, it was happening much more often. So, we moved that command into a small one line program such as A.PRG that we call when we click on a button. Having that command externally to the form helps. But, that says it all. What is going here?

Michel,

Did you consider using VFP as automation server?
oVFP = CREATEOBJECT("VisualFoxpro.Application")
oVFP.DoCmd("BUILD EXE X:\MyMainDevDir\MyApplication\MyEXE.exe FROM X:\MyMainDevDir\MyApplication\MyProject")
oVFP = Null
--sb--
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform