Hey Steve,
Although it might be possible to modify the Run-Time copy of the client's file globals, I don't know if I would recommend doing it. I should have probably mentioned this before, but this really goes against the whole concept of file globals. They are only supposed to be accessed by sequences contained within that specific sequence file. In other words you are trying to access a variable outside of its scope.
There may also be some unintended side effects that make this a poor design choice. For example, you are now imposing a requirement that all client sequence files have certain file globals which will make your test system less modular. Debugging will become more difficult as well.
All this aside, there are a few possible solutions. One option is to create a new callback within the process model. You can override the new callback from within your client sequence file, and from here pass any information you need from the process model to the client sequence. Another solution is to just store the information in the process model, and access it through the RunState.Root property within the client sequence file.
If you want to explain your application a little more, with specifics on what you are wanting to do, we might be able to provide some better solutions.
Pat P.
Software Engineer
National Instruments