You can build Windows apps today that can watch things.. UI updates, changes in variable values, etc. I don't think we can have an application be aware of open tables without a lot of work. The common way to connect to data in ,Net is through some type of data provider. Think ODBC, but there are other options. Just as in VFP, you can't be aware of what ODBC has open behind the scenes, you can't be aware of that in .Net. To make it work, you'd have to handle all the file open/close/etc yourself. I'm not sure it gains us that much to maintain all that code.




>Hi All,
>
>In 2015 Microsoft introduced the phrase 'Windows Desktop Apps' for PC-applications. This month they demonstrated the preview of the ‘Desktop App Converter’. The claim is that legacy apps can run without much adaptations inside a 'container'. Moreover, extensions can be built with the legacy platform, but also with newer platforms.
>
>I interpret this as the claim that, in time and gradually, we can build new modules and/or replace existing modules with another tool/language. Eventually the application might be totally VFP-free. However, esp. one question pops up:
>
>Modules (.app) in VFP are aware of the open tables/cursors, the public/private variables and the various SETtings. Will we be able to build a module with such a new tool/language that is also aware of open tables/cursors and variables??