>Dear all,
>
>Recital (www.recital.com) just recently announce that Foxpro would be support on the DotNet platform. How is this possible when even MS is saying this is only possible if we lose a lot of functionality? Any input would be appreciated. Thanks.

My impression is that "Mirage" (get it ?) is simply translating the "UI calls" (eg. SPR's) from "character-based" (ie. >>>DOS<<<) FoxPro apps to HTML and feeding them to a browser. The "app" itself is running on an "application server", which sounds like the same thing as a "host" machine in a PCAnywhere setup. Since DOS programs under Windows can "run in a box", "Mirage" is probably substituting as the "box" for the DOS Fox apps and in the process performs the UI translation (like a "shell"). More than one person has developed a FoxPro "decompiler"; part of implementing Mirage may involve something similar. Even VFP allows one to save Forms as HTML ... and VFP supports GETS which "internally" are actually Textboxes.

There is "little or no additional development effort" ... which probably means: no INKEY(), MDOWN(), WAIT WINDOW, etc. etc.

Remember that "browsers" work on the premise of "stateless" transactions/connections. If all your app does is collect some data in a "screen" and "submits" it for processing when a "save" button is pressed, then there may be "little or no additional effort"; otherwise, ....

How closely all this ultimately matches the ".NET" architecture is subject to debate.