3 replies to this topic

[Sindre Solem]

Is there any way of importing functions in a runtime environment without going through $XFR?

[Cleve Haynes]

There is, but I wouldn't necessarily recommend it!

You can you isout to export records from genfile.pro, functdef.pro & msgf.pro (use -s & -e switches to select the records you want). Then use isin to put the records into the run time environment.

If you don't get it exactly right, it could cause problems...

You could also write your own routine to do what $XFR does... but there is no point reinventing the wheel...

[Sindre Solem]

Most of the options in $XFR is needed for importing development specs.

Updating a function at a customer's system, with a severely non-techical operator at the other end can be quite a frustrating task, often involving telling the operator how to use Windows Explorer, etc. Making a fully automated system for importing updates means time saved and errors avoided.

[Chris Pepper]

A long time ago we developed a 'wrapper' for $XFR to allow run-time functions to be installed on-site. It does a reverse $XFR first (e.g. takes a copy of what was there) before moving in the new functions. This allows the new code to easily be un-installed. We've rather too much investment in the s/w to give it away but I can probably give some pointers to you on how to drive $XFR from separate screens.