I had already investigated that, VIEW invokes the one in TCC's directory. Help\About reveals that that v.exe may be special (to interavt with TCC).If you invoke the v.exe binary in the TC installation folder, it shouldn't work - my guess.
I guess VIEW invokes v.exe and it might be finding your v15 in the path before the one in the TC folder. Not really anything TC needs to be concerned about. Help about (within V) will answer the question because the license for TC is unique and separate from your V license.
VIEW in v19 will require a TCMD v19 license.So VIEW in the v19 release will work without a license? I doubt so but that's how your comment reads. More like v19 release won't have the restriction requiring a v18 license but will require a v19 license, right?
So will v19 include v15 of V?