HI Vijay;

  Is your App(s) using the PFC Framework?  I ask this because this sounds like old PFC code.

Regards .. Chris

Hi Chris,

Yes, the application uses PFC Framework.

I understand this issue should not be because of PFC Framework. But can you please confirm.

Thanks.

Hi, Vijay -

1. Are you running the app in PB 2022 R2 in 32-bit or 64-bit? If you are attempting to migrate to 64-bit, try 32-bit first.

2. What version of the PFC libraries are you using?

3. Is the code that calls these API functions part of the PFC objects and if so, which PFC objects, or is this code in locally-developed objects?

Best regards, John

Vijay -

I've looked up the documentation for the various API functions you listed. One major issue I see from what you provided is that many of those API functions reside in spoolss.dll, not in winspool.drv. Another difference is that many of the API functions return a Boolean value.

Here are the external function declarations I would use if I were coding this:

FUNCTION Boolean OpenPrinter ( &
   String      pPrinterName, &
   REF Longptr phPrinter, &
   Longptr pDefault &
   ) LIBRARY "winspool.drv" ALIAS FOR "OpenPrinterW"

FUNCTION UnsignedLong StartDocPrinter ( &
   Longptr         hPrinter, &
   UnsignedLong    Level, &
   REF str_docinfo pDocInfo &
   ) LIBRARY "winspool.drv" ALIAS FOR "StartDocPrinterW"

FUNCTION Boolean StartPagePrinter ( &
   Longptr hPrinter &
   ) LIBRARY "spoolss.dll"

FUNCTION Boolean WritePrinter ( &
   Longptr          hPrinter, &
   String           pBuf, &
   UnsignedLong     cbBuf, &
   REF UnsignedLong pcWritten &
   ) LIBRARY "spoolss.dll" ALIAS FOR "WritePrinter;ansi"

FUNCTION Boolean EndPagePrinter ( &
   Longptr hPrinter &
   ) LIBRARY "spoolss.dll"

FUNCTION Boolean EndDocPrinter ( &
   Longptr hPrinter &
   ) LIBRARY "spoolss.dll"

FUNCTION Boolean ClosePrinter ( &
   Longptr hPrinter &
   ) LIBRARY "spoolss.dll"

To help ensure these declarations will work in 64-bit, I have specified Longptr as the datatype for any parameter that holds a Windows handle. You should use the Longptr datatype in your code for these values.

Here is the URL I used for the OpenPrinterW API function documentation:

    https://learn.microsoft.com/en-us/windows/win32/printdocs/openprinter

All of the documentation for the other printer API functions you are using are accessible via the sidebar on the web page listed above. In each case, the name of the DLL that contains the API function is listed near the end of the function's documentation page in a table.

I suggest you check the return value from each API function call to check for error conditions... that's always a good idea as it should help you determine which function(s) are not performing as intended.

Best regards, John