Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
286
Thin Client/WindX / Re: Printing from Application Server
« on: August 22, 2018, 01:06:19 PM »
I'm going to have to defer to others for deeper details, as I have not used Application Server. These are just items that I would have anyone check if they're having local printer problems.
287
Thin Client/WindX / Re: Printing from Application Server
« on: August 22, 2018, 12:38:04 PM »
Which did you type:
OPEN (1)"[lcl]*winprt*"
or
OPEN (1)"[lcl]*winprnt*"
...?
Be sure it's the first...
OPEN (1)"[lcl]*winprt*"
or
OPEN (1)"[lcl]*winprnt*"
...?
Be sure it's the first...
288
Thin Client/WindX / Re: Printing from Application Server
« on: August 22, 2018, 12:13:36 PM »
I'm guessing that you're running on a Windows server. Try:
OPEN (1) "[lcl]*winprt*"
OPEN (1) "[lcl]*winprt*"
289
Nomads / Re: Logic with Numeric Multi_lines
« on: August 17, 2018, 10:44:25 AM »Quote
whenever the user changes the field in the control, the numeric field is synchronized. If the field value is changed by the user entering data or by browsing, etc., the fields are synchronized, so it doesn't really matter which one you use.Jane, on this one, I beg to differ. The only place that I see the STR_TO_NUM being used in the F/M is at WRITE time. And I don't think *winproc knows whether it's supposed to maintain both values (though I haven't gone too deep into that). (NUM_TO_STR is used in FIND_REC, WRT (post-write), DISP_REC, and CLEAR_FIELDS.)
Which suggests, again, that everything be handled with the strings, and only the actual file contents are numeric.
290
Nomads / Re: Logic with Numeric Multi_lines
« on: August 16, 2018, 11:07:33 AM »
Yes, that works as designed, but I want to be able to use the contents of that value (in this case a "Length") to determine the specifications for a different control.
Should I use a Numeric control for the file's numeric field? Or should I use num(Control$) and make it a non-Numeric control?
Should I use a Numeric control for the file's numeric field? Or should I use num(Control$) and make it a non-Numeric control?
291
Nomads / Re: Logic with Numeric Multi_lines
« on: August 16, 2018, 10:44:54 AM »
Does anyone have some clarification?
292
Off Topic / Re: Label Printer Suggestions
« on: August 14, 2018, 03:30:13 PM »
Are you looking for an impact printer or a Zebra-type printer?
293
Nomads / Re: Logic with Numeric Multi_lines
« on: August 10, 2018, 10:10:26 AM »
I guess that calls into question whether I should set up the control as Number if the data field is numeric. In the generated F/Ms, the Num_To_Str routine is called after reading the record, and Str_To_Num before being rewritten. Which suggests I should use the controls as strings, not numbers, even though the underlying file variable is numeric.
Clarification? Is this the way to go?
Clarification? Is this the way to go?
294
Nomads / Re: Logic with Numeric Multi_lines
« on: August 10, 2018, 09:48:51 AM »
But if I have a numeric field variable, do I use the Field_Name or Field_Name$ in the procedures?
295
Nomads / Logic with Numeric Multi_lines
« on: August 09, 2018, 03:20:08 PM »
I'm using a generated File Maint program to work on a file that has numeric fields in it. When I want to refer to these values in Logic procedures in a multi_line, I seem to get inconsistent results. Which of these should I actually use?
Thanks!
- Field_Name
- Field_Name.Ctl'Value
- Field_Name$
- Field_Name.Ctl'Value$
Thanks!
296
Programming / Re: File maintenance panel creation for flat files,
« on: August 03, 2018, 05:35:14 PM »
As Jane had suggested, "try doing a LOAD "*win/flmaint" to see if you have access to the file."
From command mode, type:
LOAD "*win/flmaint"
If the program loads, then there is something else that is the problem. If not, then be sure your PREFIX and/or Working Directory (lwd) and/or Home Directory (hwd) include the path to your PxPlus lib directory. Once that is set, you should be able to proceed.
From command mode, type:
LOAD "*win/flmaint"
If the program loads, then there is something else that is the problem. If not, then be sure your PREFIX and/or Working Directory (lwd) and/or Home Directory (hwd) include the path to your PxPlus lib directory. Once that is set, you should be able to proceed.
297
Programming / Re: PxPlus 2018 closing when trying to use key number 17
« on: August 01, 2018, 09:47:20 AM »
If I recall correctly, PxPlus keyed files only support 16 keys.
298
Language / Re: Update a LIST_BOX
« on: July 25, 2018, 01:06:42 PM »
Here's a variation on that theme, without having to actually remove the existing item:
Code: [Select]
0010 print 'CS'; list
0020 My_List=100
0030 list_box My_List,@(2,14,12,6),fnt="*"
0040 list_box load My_List,"Dog/Cat/Pig/"; wait 1
0050 My_List'FindItemText$="Cat" ! Locate the item to change
0060 My_List'ItemText$="T-Rex" ! Load this one in its place
0070 wait 3
0080 ! list_box remove My_List
0090 end
299
Programming / Re: WAIT FOR EVENT example - Error 49
« on: July 18, 2018, 10:03:42 AM »
Based on the examples, both above and in the documentation, there seems to be an ENABLE EVENT directive missing.
300
Wish List / Re: gosub SOMEWHERE with a$=b$
« on: July 13, 2018, 09:37:49 AM »
You can pretty much already do that with a CALL into the current program:
CALL pgn+";routine_name",addrx$
CALL pgn+";routine_name",addrx$