Indeed it is split. The situation is this.
An application is heading off to 24 sites over the next month. It is built and has been tested over a month at 4 sites. However there is one small part missing, as I have been waiting on someone else to complete. Essentially I don't want to roll this out to all parties only to do it all again for the addition or change of one function. My thoughts were this, do tell me if this is wildly wrong conceptially. To provide the text for this one function, as it currently stands, in a txt file in a defined subfolder. The application will then create the function from this. Therefore when everyone else has got their act together and given me the final details I will be able to re issue the txt file via email, each user will, as it is within their skill base, replace the existing file with the new one and the application will read this in instead.
I've covered aspects of different BE locations, and differing references and their locations even in the runtime versions and this seems to be the final piece.
I have looked at the code in the link and it does indeed perform what i was hoping to achieve. Are there any draw backs? known shortfalls or issues with using this? I infact only needed the one line: Application.LoadFromText
Thanks again
Dan