Skip to main content

SOLVED: Logical Printer defs from old INI to new INI

Author: knut.dybendahl@gmail.com (Knut)

In a larger deployment environment where each PC has its own copy of the INI file, the printer mapping is stored in the INI file (under [printer]) and in the registry for that user. However, when migrating between, say 9.3 and 9.6, the INI file must be upgraded / changed to accomodate new widgets and the [paths] settings. Does anyone have any best practice examples on how to drag the old LOG_PRINTER line from the 9.3 ini to the new 9.6 ini - without *manually* doing it?? Cheers,

SOLVED: Logical Printer defs from old INI to new INI

Author: knut.dybendahl@gmail.com (Knut)

In a larger deployment environment where each PC has its own copy of the INI file, the printer mapping is stored in the INI file (under [printer]) and in the registry for that user. However, when migrating between, say 9.3 and 9.6, the INI file must be upgraded / changed to accomodate new widgets and the [paths] settings. Does anyone have any best practice examples on how to drag the old LOG_PRINTER line from the 9.3 ini to the new 9.6 ini - without *manually* doing it?? Cheers,

Hi Knut, You can use the $setting proc to fetch and write to the values that you require for .ini files as well as .asn files I believe? Ronny


Author: rkrite (rkrite@gmail.com)

SOLVED: Logical Printer defs from old INI to new INI

Author: knut.dybendahl@gmail.com (Knut)

In a larger deployment environment where each PC has its own copy of the INI file, the printer mapping is stored in the INI file (under [printer]) and in the registry for that user. However, when migrating between, say 9.3 and 9.6, the INI file must be upgraded / changed to accomodate new widgets and the [paths] settings. Does anyone have any best practice examples on how to drag the old LOG_PRINTER line from the 9.3 ini to the new 9.6 ini - without *manually* doing it?? Cheers,

Hi Ronny, I looked at that - but according to the manual [printer] cannot be set (if I interpreted it correctly)... I'll have another look. Cheers


Author: Knut (knut.dybendahl@gmail.com)

SOLVED: Logical Printer defs from old INI to new INI

Author: knut.dybendahl@gmail.com (Knut)

In a larger deployment environment where each PC has its own copy of the INI file, the printer mapping is stored in the INI file (under [printer]) and in the registry for that user. However, when migrating between, say 9.3 and 9.6, the INI file must be upgraded / changed to accomodate new widgets and the [paths] settings. Does anyone have any best practice examples on how to drag the old LOG_PRINTER line from the 9.3 ini to the new 9.6 ini - without *manually* doing it?? Cheers,

Hi Knut, You can change any section of the ini file. The limitation on certain sections is only for setting runtime settings dynamically. So you can change the logical printers with $settings but you have to restart Uniface to make the settings effective. Theo


Author: Theo Neeskens (tneeskens@itblockz.nl)

SOLVED: Logical Printer defs from old INI to new INI

Author: knut.dybendahl@gmail.com (Knut)

In a larger deployment environment where each PC has its own copy of the INI file, the printer mapping is stored in the INI file (under [printer]) and in the registry for that user. However, when migrating between, say 9.3 and 9.6, the INI file must be upgraded / changed to accomodate new widgets and the [paths] settings. Does anyone have any best practice examples on how to drag the old LOG_PRINTER line from the 9.3 ini to the new 9.6 ini - without *manually* doing it?? Cheers,

Hi Theo, Thanking you - it was the restart bit I was missing.... Knut


Author: Knut (knut.dybendahl@gmail.com)
Terms & ConditionsAccessibility statement