PxPlus User Forum

Twitter Twitter Twitter

Recent Posts

Pages: [1] 2 3 ... 10
1
Programming / Re: *CONTROL displays error 12 popup
« Last post by Mike King on Today at 01:45:18 PM »
It always was $CTL-xxx not _CTL-xxx; however you indicated that _ctl-999 worked which would tend to indicate you have a custom *CONTROL program since $CTL was the program name used ever since the being of ProvideX or PxPlus.
2
Programming / Re: *CONTROL displays error 12 popup
« Last post by MikeinFL on Today at 01:28:20 PM »
Was not a typo.  I changed file name from _CTL-999 to $CTL-999 and it works ok now in PxPlus.  Thanks! 
3
Programming / Re: *CONTROL displays error 12 popup
« Last post by Mike King on Today at 12:13:01 PM »
I just tried this on my machine here and didn't have any problem.

I saved my program $CTL-999 (not _CTK-999 as per your post which I assume is just a typo)

I then set $01$ (which is CTRL-A) to generate -999 and then pressed CTRL-A .
Make sure you file names, file name case, and prefix rules are correct.

Screen shot attached.
4
Programming / *CONTROL displays error 12 popup
« Last post by MikeinFL on Today at 11:29:31 AM »
I have a button -999 in a program.  I have my _CTL-999 program in my app folder.  Using ProvideX v5 it the button runs my -CTL-999 ok.

Same code using Pxplus 2017 v14.10.0000 and 2019 v16.20.0000I get an error 12 popup box. 

As a test, I renamed *CONTROL in 2017 \lib\ and copied the old *CONTROL from ProvideX to it.  I no longer get error 12 box with my button and _CTL-999 and they work. 

I need my button -999 to work.  The newer *CONTROL is pw protected.  Is it ok just to use the old *CONTROL program in PxPlus?  Is there a quick fix or should I submit as a ticket?

Thanks Mike
5
Programming / Re: Printing to PDF - through WindX/Citrix connection
« Last post by Mike King on March 27, 2020, 03:28:10 PM »
This sounds like you might have either a bad or missing libhpls.dll in the WindX installation or perhaps a version mismatch if you updated the EXE and not the PDF DLL.

I would try to reinstall WindX.
6
Programming / Re: Printing to PDF - through WindX/Citrix connection
« Last post by Dave Fullerton on March 27, 2020, 03:17:02 PM »
Thanks to Mike's suggestion, I now know what is going on - MSG(-1) says "Unable to load/locate functions from PxPlus PDF Library (err/ret=13/127)

MSG(RET) returns Permission denied.

Do I re-install Windx?

Regards

Dave
7
Programming / Re: Printing to PDF - through WindX/Citrix connection
« Last post by Dave Fullerton on March 27, 2020, 02:43:49 PM »
Hi Mike:

I was printing MSG(RET) and was getting something like I would get for an error 12 - didn't think about trying a [wdx]print msg(-1).  Msg(-1) didn't give me anything, but of course, that was relative to the server.

I'll give the [wdx]msg(-1) routine a shot - thanks

DAve
8
Programming / Re: Printing to PDF - through WindX/Citrix connection
« Last post by Mike King on March 27, 2020, 02:33:20 PM »
As a followup -- since WindX is involved the error 15 may be occurring on the workstation so you may need to get the error information from the workstation either by:

  • Issuing a EXECUTE "[wdx]PRINT MSG(-1)" to display the error
  • CALL "[wdx]*windx.utl","MSG(-1)", X$ then print X$ to see the error information

You might also try to simply create the PDF file on the workstation using:

SERIAL "[wdx]testfile"

Change testfile to wherever on the workstation you want the PDF file to ultimately be created.
9
Programming / Re: Printing to PDF - through WindX/Citrix connection
« Last post by Devon Austen on March 27, 2020, 02:21:27 PM »
An error 15 is an OS error. If you print MSG(-1) you can sometimes get more info about the error. This info may help you figure out the problem.
10
Programming / Printing to PDF - through WindX/Citrix connection
« Last post by Dave Fullerton on March 27, 2020, 02:14:53 PM »
Hi Folks:

Running into an error 15 attempting to write to [wdx]*PDF* when the WindX user is connected via a Citrix server to our application server.  All works as expected if the user does not go through the Citrix server (i.e. they are in their network).   It looks like a convoluted setup to me.

We can create a folder for the file to reside in, and a file name is displayed in the folder, but then the error 15 occurs and an invalid PDF file (adobe can't read it) that is 2K in size is left.

PxPlus on the server is V12, PxPlus on the WindX is V15 (we are getting ready for an update).

Unfortunately, we can't trace the PDF on the WindX station.  We suspect that the issue is permissions based, but the folder is set for Everyone with full access.

Does anyone have any suggestions what we might do for a solution?

Thanks

Dave Fullerton
Pages: [1] 2 3 ... 10