>PMFJI,
>
>What is the relevance of this tool anyways? GoFish goes through my 30+ MB project in only 2 seconds and presents me with the files which contain a word (SDD Harddisks are wonderful quick for this purpose).


That tool is basically a file finder. I don't know what GoFish does but for this tool "30+Mb in only 2 seconds" is considered to be extremely slow. I can find a given file on my multiple disks (2+Terrabytes) instantly.



>>Well I am not sure that VFP is still "clever" (anything further I say would cause flames and blames as if I don't like VFP or still using it extensively - some kind of defensive act for any language users maybe).
>
>Depends on how you define clever. If you look at the web stack (we are using SQL Server, C#, JSON, JQUERY, JavaScript and HTML 5), you can hardly argue that this is clever. There are SAAS products out the like Windev, Lianja,, Servoy that do all of it in a much more clever way. But for some reason we choose for 'more control' and not being trapped in a 'vendor lock-in'.

VFP too is a vendor lock-in. I don't use those lianja, servoy ... so I really didn't understand what you meant here. He was saying something like VFP is a clever language to handle creating something like that "everything" tool and I meant it was not. I really don't have an idea what actually "clever" means for a language. I got that "tool that has capability to do it". I doubted.

>
>As for VFP, it is what it is, Its still is relevant for us as our main product is still written in VFP and we are only phasing this out in the next 5 years. The 'clever' thing in VFP that is still relevant is that is more RAD than the web stack style of development. We however do not use DBFs, but use SQL server exclusively. We use commandbars to replace the outdated GUI from VFP with a more modern style of menus and themes. Our application does not look like a VFP app, but it is. We use crystal reports for reporting rather than the build in report engine (even though its not that bad, crystal is more versatile).
>
>We found that VFP is a very good choice for middleware like running HL7 services. Easy to make changes in handling messages and runs surprising stable. We most likely will never rewrite those in another language until it becomes a problem in finding or training VFP developers.
>

Yes, VFP is what it is. You also use more and more external engines to do things as you say.

>
>To me, this would be sign of bad organisation of your source files if you need such functionality on a frequent basis. I can see that you might want to search something in your project file on a daily basis, but if you have to do this daily for your whole HD or worse, several computers where you might have stored it, then I would think something else is wrong.
>
>
>But I agree with your message. Do not try to re-create something that already exists in VFP just for the sake of it. I, for one, have better things to do.
>
>Walter,

:) Maybe it is my bad organization. Mind you we are not talking about just VFP projects and I don't use a single language. Even if it were, it wouldn't change the fact that I need to find a file on disk that may have saved long ago and I don't remember the location. You have good organization and perfect memory then it is good for you, you don't need a tool like "everything".