>Hi everybody,
>
>There are couple of internal VFP things, which lead me to some frustration and problems with new versions.
>
>First problem is: When application (.app) executes on user's machine, it automatically resides in memory, so there is no way to update this application, without kicking everybody out. I know about different "launcher" approaches, but we haven't implemented any of them so far, so this is still a real problem for me (and my colleagues) as developers.
Launcher approach is the best. :)
>
>The second problem is: If a table is part of a database, and it's used in a form with private DS, the database remains open after form is closed. How are you dealing with this problem?
CLOSE DATABASES
:)
>
>Thanks in advance.
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison