Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Was expected to be fixed but it's not
Message
 
À
08/03/2003 15:21:22
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00760584
Message ID:
00777092
Vues:
41
Hi Michel,

Did you ever solve this? I've got a project converted from VFP6 that exhibits this behaviour. In fact, I can not get it to build at all. I've recreated the project from scratch, and still no-go.

Cheers,

Andrew

>>Maybe I'm missing something but error message "Compile error in file d:\vfpclien\www\universa.app" says that there's problem/error compiling universa.app. It isn't COM object.
>
>If it would be an error from the project at compile time, that would mean the compilation would work. In my case, it isn't. There is also no error in the project. Basically, it's quite simple, when it does that, I just restart my application and click again on compile and it works. So, no change in the code, not even one task manager flip to the development environment. This is intact. I just restart my application (the console monitoring for compiling and uploading to server), retry and it works.
>
>As I said, this is a problem with how Visual FoxPro handles its memory management. I really don't understand that but something got stuck in memory sometimes and this is why I only face this situation occasionnaly.


If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?


From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."


All my FoxTalk and other articles are available on my web site.


Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform