one of my guys found out that if you check the box "export based on session", the file dump.l has way too many components listed, even those you don't need "based on session". it has components that do not belong to the sessions, even the objects in object modelling.

infor's explanation was:

"The program script has not been updated in a long time. When based on session is selected, not only components belonging to this sessions are exported, but also library, dal, etc. programs scripts. All of them for that VRC. This is done because we cannot determine which script library possibly could be used by the session. There is no way to stop the export from exporting these extra scripts.There are no plans to change this.So yes, the session works as was planned, though it might seem confusing."

has anybody else observed this? i thought this makes the box unusable unless you uncheck it and select the session, reports, scripts, forms you want to export/import. when this session came out in 1998 it's supposed to be a faster way of exporting and importing selectively based on session, so you don't need to select forms, reports, etc individually. it should pick up the components "based on session".

has anybody else observed this? i thought this makes the box unusable unless you uncheck it and select the session, reports, scripts, forms you want to export/import.
Yes, observed it before. What are you trying to achieve? The new way for code migration is with PMC sessions.

Refer to the thread - Development question: about the Deployment (http://www.baanboard.com/baanboard/showthread.php?t=56639&highlight=ttpmc1100m000)

yes i use pmc too. i find this old export/import session fast when moving objects between my dev and test boxes. the functionality known to me is you can select "based on session" and the program is supposed to pick the forms/scripts/reports/etc based on the session number on your input field.