Well, as described in the thread above, this is not a terribly good way of doing it because it depends on the interactive forms having been run. What has happened here is that the original poster will have used the interactive move command in the layout editor, and typed in values on fields on the form - and then captured the commands in the CDS.log (and the CIW if the log filter settings are set appropriately) which record how the form was filled in. In general we don't document those - they're there to enable replay of the log file in the same conditions. In this case the form has a number as part of it - I think (if I remember rightly) this is because we keep the form unique for different technologies (may be for different windows - I didn't check). Anyway, the point is that this is precisely why you don't want to be using this approach to do your automation, as it relies on both undocumented behaviour, and also potentially the form name may change depending on what you've done before. Hence the suggestion to use the dbMoveFig approach.
↧