Recent posts

#21
Programming / Re: API Call returning unreada...
Last post by Devon Austen - April 13, 2026, 01:52:10 PM
Support for the use of HTTP version 1.1 protocol was added in PxPlus 2021 (v18.00).

If you are using an earlier version it is always using HTTP 1.0.
#22
Programming / Re: API Call returning unreada...
Last post by gmundt - April 13, 2026, 12:57:24 PM
I thought that call "*plus/web/request" defaulted to 1.1 and would need to update %web_request_http_ver$ to change it 1.0.
#23
Programming / Re: API Call returning unreada...
Last post by James Zukowski - April 13, 2026, 08:41:22 AM
It looks like you're using HTTP 1.0. FedEx may be expecting 1.1.
#24
Language / Re: accessing the viewer thru ...
Last post by Mike Hatfield - April 10, 2026, 07:19:36 PM
You add a Local Text Printer in Windows Devices and Printers and call it "yourname Viewer"
Add Printer
Create a new port - Local Port
Name of Port - NUL:
General  - Generic / Text Only
Print Name 'yourname Viewer'
Then open *winprt* etc
#25
Language / accessing the viewer thru wind...
Last post by Jerry Fletcher - April 10, 2026, 02:15:01 PM
Hello List,

I might have totally imagined this but I swear at one installation I saw the pxplus viewer listed in the windows printer list.  If I'm not imagining it we could really use this. 

.has anyone ever seen this?

Jerry
#26
Programming / API Call returning unreadable
Last post by gmundt - April 10, 2026, 02:00:04 PM
I am trying to make an API call to FedEx rate quote.  The JSON works fine in Postman, but when I attempt it through the web/request I am getting unreadable response.

extrahdr$="Content-Type: application/json"+$0a$+"Authorization: Bearer MyToken"+$0a$+"Accept-Encoding: identity"

url$=https://apis-sandbox.fedex.com/rate/v1/rates/quotes

request$=
{
  "accountNumber":{
    "value":"740561073"
  },
  "requestedShipment":{
    "shipper":{
      "address":{
        "streetLines":["17841 FITCH"],
        "city":"IRVINE",
        "stateOrProvinceCode":"CA",
        "postalCode":"92614",
        "countryCode":"US"
      }
    },
    "recipient":{
      "address":{
        "streetLines":["7609 Geranium Street"],
        "city":"Bethesda",
        "stateOrProvinceCode":"MD",
        "postalCode":"20817",
        "countryCode":"US"
      }
    },
    "rateRequestType":["LIST"],
    "serviceType":"FIRST_OVERNIGHT",
    "preferredCurrency":"USD",
    "shipDateStamp":"2026-04-10",
    "pickupType":"DROPOFF_AT_FEDEX_LOCATION",
    "packagingType":"YOUR_PACKAGING",
    "requestedPackageLineItems":[
      {
        "groupPackageCount":"1",
        "weight":{
          "units":"LB",
          "value":"8"
        }
      }
    ]
  }
}

method$="POST"

call "*plus/web/request",url$,request$,rcv_data$,rcv_hdr$,"","",extrahdr$,method$

Since the header is returning HTTP/1.0 500 Internal Server Error and Content-Encoding is returning gzip I believe I have something incorrect in the heading.

 
#27
Language / Re: winqry ERR=42
Last post by edjack - April 08, 2026, 09:22:40 PM
We have several clients that report this ERR=42, Program: winqry, Line: 01875
One client reports that our app is just on one computer but they use different Windows user Ids and Just ONE User ID reports the error. The other users report no errors.
What does this tell us?
#28
Language / Re: winqry ERR=42
Last post by edjack - April 08, 2026, 05:58:35 PM
we have no query's that even come close to 200 columns.
It must be something else.
#29
Language / Re: winqry ERR=42
Last post by Jane Raymond - April 07, 2026, 09:05:39 AM
If the version is 13.10, then line 1875 is:
1875 LET _HideCol=NUM(_HideOpts$(i,1))
Error 42 would indicate that the subscript i is out of range. The _HideCol array is dimmed to 200, so if you have more than 200 columns in your query, this would cause the issue.
#30
Language / Re: winqry ERR=42
Last post by Devon Austen - April 06, 2026, 11:03:23 AM
Is this still version 13.10?

If you open up that program on the system that gets the error is there a line 1875 and if so what is that code?

If there is no line 1875 you may have to open up a trace window and then cause the error to happen and then look through the trace.

Can you bypass your error handling to see if you can get the real line number?