Post Error Label Not defined - Custom Questions/Prompt

[MachiningPartner]

Hi guys

hope all are well.  How to properly omit custom prompts during posting? I located custom questions in the .pst file and just added # in from of it under fq and pheader. Now prompts are not showing up but post error   "The post block output type processing has failed!, Label has not been  defined"    appears. The program posts fine, just how to correct the error?

fbuf 6 0 255 0 1
# --------------------------------------------------------------------------
# Question format statements
# --------------------------------------------------------------------------
fq 1 stock_typ "Predator Stock [0=Box,1=Cylindrical]"
fq 2 cyl_typ "Cylindrical Stock Axis [1=X,2=Y,3=Z]"

# --------------------------------------------------------------------------
# Custom questions
#fq  50  scust_nom     "Customer Name?"
#fq  51  sprt_no       "Part number?"
#fq  52  srev_lev      "Revision level?"
#fq  53  sprt_nom      "Part name?"
#fq  54  sop_no        "Operation number?"

------------------------------------------------------

 

#scomm_str, scust_nom, scomm_end, e$
      #scomm_str, "P/N", 32, sprt_no, 32, "REV.", srev_lev, scomm_end, e$
      #scomm_str, sprt_nom, scomm_end, e$
      #scomm_str, "OPERATION ", sop_no, " OF ", sops_no, scomm_end, e$
      #scomm_str, "GENERATED", 32, sed_lst, 32, scomm_end, e$
      #scomm_str, "LAST EDIT", 32, sed_lst, 32, scomm_end, e$
      #scomm_str, "PROVEN M/C", 35, "1 ", sed_lst, " ??", scomm_end, e$
      #scomm_str, "CYCLE TIME = ??.?? HRS.", scomm_end, e$
      #scomm_str, sm00, scomm_str, "**UN-PROVEN PROGRAM**", scomm_end, e$
      spaces$=sav_spc

[nickbe10]

On 9/25/2020 at 9:13 PM, MachiningPartner said:

just how to correct the error?

You have an undefined situation (variable?) on line 2445 of the post, or in the post block which begins on line 2445.

[MachiningPartner]

The  .PST was correct but the error was from the .psb, which is encrypted binary file and we had to contact and pay (maintenance expired) the reseller to address.  It would not be ideal from consumer perspective if we have to pay reseller each time to edit the .psb file, even if we edit the .pst correct.

[nickbe10]

17 minutes ago, MachiningPartner said:

It would not be ideal from consumer perspective if we have to pay reseller each time to edit the .psb file, even if we edit the .pst correct.

That's the advantage to keeping maintenance up to date. Almost all third party purchased posts come with some sort of encryption.

This makes managing the file easier for the post editor.

Imagine if you sold someone an "open" post, they go in and try and "fix" something, they make a mess of it and then send it back to you and ask you to fix the mess. 

It has happened to many times to mention, and so people protect themselves and their work.

[JParis]

42 minutes ago, MachiningPartner said:

It would not be ideal from consumer perspective if we have to pay reseller each time to edit the .psb file, even if we edit the .pst correct.

The software changes over time...thus, what may have previously worked in a post before can no longer work properly if enough time passes....

Don't know who you purchased your post through but we have post maintenance on our purchased posts...just for this kind of reason...kind of like insurance, it might be a pain to pay but if you don't and you need it, it's gonna hurt.

It's actually a really good deal for consumers....you don't have to spend the majority of the development time, then you don't have to worry about the long term viability of what you purchase. Otherwise, you are stepping over dollars to save dimes.