Windows Environment Variables With Commander? Follow
Does anybody happen to have an example of using environment variables with Commander scripts? I have a system creating data files, which contain hard-coded specifications of which label template to use and a hard-coded printer name. For ease of use, my preference is to have the system that exports the data files use more generic names for both of these, so that only the Bartender server system happens to know or care about the exact name of the label templates or the printers. I think I can handle both with windows environment variables...?
Is there a better practice than this approach for what I'm trying to do, as I build to dozens of printers and label templates?
EDIT: Seems like Commander won't work with WEVs. I have %TESTTEMPLATE% as an entry and when I navigate to that in windows explorer it pulls up the template, but when I put it into an otherwise-functioning commander script nothing happens; in the Commander log I see the AF=%TESTTEMPLATE% , but never get a print. When I change back to the hard-coded, which %TESTTEMPLATE% points to, it works.