>I've actually heard from the lead developer in mid-December, but his prediction of a release the next week did not come true. I'm not sure what the hangup is: the major pieces to be implemented are down to the grid and rushmore (the latter being the key to making SQL Select work effectively against DBF's, including their new 64-bit dbf's). The other functionality is pretty much all there, including cursoradapters (at least the class is there, and supposedly they work for some scenarios). It would be a real shame if they were to fail this close to the finish line. That's the main point that gives me hope: they are this close. In addition, they have a dynamite marketing plan that will ensure they become known to all sorts of non-VFP developers, and it's something they have a capacity right now to carry out, without additional resources.
>
>Hank

A dynamite marketing plan?

They'll have to ensure they are known by all sorts of non-VFP developers since they've missed that opportunity (to market to VFP developers) pretty much completely by now. Then they'll have to convince non-VFP developers that there is some reason to use their VFP syntax rather than the incredibly broad and powerful .NET framework that has been building for almost a decade.

I assume the VFP compiler isn't their day job since they have no communications or marketing to speak of, and since their progress seems to be extremely slow. I think they'll be able to count paying users on their fingertips if it is released.

BTW I was excited about it a couple of years ago. I really was.


>
>>>So far as I know, the VFP Compiler for .Net runs on Mono now; or at least it did as of last Spring (at which time I believe it was actually being developed on Mono).
>>>
>>>As for whether it will be completed: who knows? Do you have information on this issue?
>>
>>No information is coming from the people behind the VFP Compiler for .Net for a long time. That's one of the reasons I think it's not going to be complete anywhere soon