Hi,
A multi-part question:
1) When a user prints a PO during posting from the PO Entry Screen they get an error message saying "ERROR: LoadLibrary". I've confirmed the error by trying it myself and ensuring I'm selecting the correct report. I've read many places this is related to datapipes, but I'm not sure exactly which of the datapipe lines to remove? Also, can i edit the crystal=POPOR01 line to the custom name of the report below to point to our custom form?
'************** Object id = PO3020 ******************
' ----- Print Purchase Order Form
[POPOR01]
type=DATAPIPE
heading=50550
crystal=POPOR01
orientation=portrait
paper size=1
optparams=13
2=PORFROM STRING 50554
3=PORTO STRING 50555
4=PRINTED STRING 50556
5=QTYDEC STRING 50557
6=ACTIVE STRING 50558
7=STANDING STRING 50559
8=FUTURE STRING 50560
9=BLANKET STRING 50561
10=DPRINTED STRING 50562
11=DELMETHOD STRING 50563
12=ECENABLED STRING 50564
13=DIRECTEC STRING 50565
14=SWDELMETHOD STRING 50566
datapipe path=..datapipe query="popoprn.dll=POPOR01\n%PORFROM%\n%PORTO%\n%PRINTED%\n%ACTIVE%\n%STANDING%\n%FUTURE%\n%BLANKET%\n%DPRINTED%\n%DELMETHOD%\n%ECENABLED%\n%DIRECTEC%\n1\n0\n0\n0\n0\n0\n0\n%SWDELMETHOD%\n"
'************** Object id = PO3020 ******************
' ----- Print Purchase Order Form
[POPOR02]
type=DATAPIPE
heading=50570
crystal=POPOR02
orientation=portrait
paper size=1
optparams=13
2=PORFROM STRING 50574
3=PORTO STRING 50575
4=PRINTED STRING 50576
5=QTYDEC STRING 50577
6=ACTIVE STRING 50578
7=STANDING STRING 50579
8=FUTURE STRING 50580
9=BLANKET STRING 50581
10=DPRINTED STRING 50582
11=DELMETHOD STRING 50583
12=ECENABLED STRING 50584
13=DIRECTEC STRING 50585
14=SWDELMETHOD STRING 50586
datapipe path=..datapipe query="popoprn.dll=POPOR02\n%PORFROM%\n%PORTO%\n%PRINTED%\n%ACTIVE%\n%STANDING%\n%FUTURE%\n%BLANKET%\n%DPRINTED%\n%DELMETHOD%\n%ECENABLED%\n%DIRECTEC%\n1\n0\n0\n%SWDELMETHOD%\n"
2) We just upgraded from 5.5A to 5.6A at this branch and this worked fine for 5.5A, but doesn't now. Is there no way to carry these setting across when upgrading or does it need to be configured for each module with custom report? I'm in the process of an upgrade project and would like some input at this could save me a lot of time over a lot of branches.
A multi-part question:
1) When a user prints a PO during posting from the PO Entry Screen they get an error message saying "ERROR: LoadLibrary". I've confirmed the error by trying it myself and ensuring I'm selecting the correct report. I've read many places this is related to datapipes, but I'm not sure exactly which of the datapipe lines to remove? Also, can i edit the crystal=POPOR01 line to the custom name of the report below to point to our custom form?
'************** Object id = PO3020 ******************
' ----- Print Purchase Order Form
[POPOR01]
type=DATAPIPE
heading=50550
crystal=POPOR01
orientation=portrait
paper size=1
optparams=13
2=PORFROM STRING 50554
3=PORTO STRING 50555
4=PRINTED STRING 50556
5=QTYDEC STRING 50557
6=ACTIVE STRING 50558
7=STANDING STRING 50559
8=FUTURE STRING 50560
9=BLANKET STRING 50561
10=DPRINTED STRING 50562
11=DELMETHOD STRING 50563
12=ECENABLED STRING 50564
13=DIRECTEC STRING 50565
14=SWDELMETHOD STRING 50566
datapipe path=..datapipe query="popoprn.dll=POPOR01\n%PORFROM%\n%PORTO%\n%PRINTED%\n%ACTIVE%\n%STANDING%\n%FUTURE%\n%BLANKET%\n%DPRINTED%\n%DELMETHOD%\n%ECENABLED%\n%DIRECTEC%\n1\n0\n0\n0\n0\n0\n0\n%SWDELMETHOD%\n"
'************** Object id = PO3020 ******************
' ----- Print Purchase Order Form
[POPOR02]
type=DATAPIPE
heading=50570
crystal=POPOR02
orientation=portrait
paper size=1
optparams=13
2=PORFROM STRING 50574
3=PORTO STRING 50575
4=PRINTED STRING 50576
5=QTYDEC STRING 50577
6=ACTIVE STRING 50578
7=STANDING STRING 50579
8=FUTURE STRING 50580
9=BLANKET STRING 50581
10=DPRINTED STRING 50582
11=DELMETHOD STRING 50583
12=ECENABLED STRING 50584
13=DIRECTEC STRING 50585
14=SWDELMETHOD STRING 50586
datapipe path=..datapipe query="popoprn.dll=POPOR02\n%PORFROM%\n%PORTO%\n%PRINTED%\n%ACTIVE%\n%STANDING%\n%FUTURE%\n%BLANKET%\n%DPRINTED%\n%DELMETHOD%\n%ECENABLED%\n%DIRECTEC%\n1\n0\n0\n%SWDELMETHOD%\n"
2) We just upgraded from 5.5A to 5.6A at this branch and this worked fine for 5.5A, but doesn't now. Is there no way to carry these setting across when upgrading or does it need to be configured for each module with custom report? I'm in the process of an upgrade project and would like some input at this could save me a lot of time over a lot of branches.