This is just a short question, maybe someone out there has some experience or insight that they are willing to share.

There is a debate raging over the best way to update VCX components from the file-server to the local drive for use.
The prevalent contention is an approach whereby the application would complete its run cycle, check for a newer version and if found, clear the classlib, copy down the newer version, spawn ( Run /N ) the application anew as another VFP instance, and then quit the original VFP instance.

My question is two fold:
  1.   Is there a simpler way?
  2.   Would such a scenario restrict the amount of memory available to the subsequent VFP instance, perhaps because the original instance is still utilizing its own memory allocations when (while) the next instance is instantiated?

I admit that I have not done any empirical testing on the matter, hoping that someone would already know; thus avoiding any 're-invention' of the wheel... so to speak.

My thanks in advance.