Simulating Dynamic File References

We use the separation model with two files, Interface file and Data file. Basically, we have one db application over Terminal Services where every client database has these two files. Hot fixes and updates are therefore a real hassle. Any changes need to be made on every file - very tedious and potentially error prone.

There is nothing we can do about the DATA file but the only difference in each of the interface files is the External Server Group Name (from Active Directory) and a File reference. You can see now the benefit of having a single interface file. Based on user login the DATA file reference would be then changed to point to the proper file.

One solution would be to create the interface file on the fly with proper file reference set and then open the new file on the server (using .NET and windows messages for examples)

Has anyone tried to accomplish something similar? Any ideas would be greatly appreciated.

Thanks,

Dali