Forms Issue

[John Kugler]

I'm having an issue with a FORM in PCDMIS. The idea is that the form pops up at the beginning of the program for the operator to enter some info.

CODE:

$$ NO,
            ====================
            ASSIGN/CNC_MACH=0
            ASSIGN/PAL_NUM=0
            ASSIGN/SER_NUM=0
            ASSIGN/SUB_TYPE=0
            ASSIGN/EMP_NUM=0
$$ NO,
            ====================
FORMLABELREDO=LABEL/
CS1        =FORM/FILENAME= C:\USERS\DESKTOP\FORM1.FORM
            PARAM/=[COLOR=#FF0000]TEXTSERNUM.TEXT=SER_NUM[/COLOR]
            PARAM/=[COLOR=#FF0000]TEXTSUB.TEXT=SUB_TYPE[/COLOR]
            PARAM/=[COLOR=#FF0000]TEXTTEMPIDNUM.TEXT=EMP_NUM[/COLOR]
            PARAM/=[COLOR=#FF0000]TEXTOPNUMBER.TEXT=OP_NUM[/COLOR]
            PARAM/=
            ENDFORM/
$$ NO,
            ====================
            IF_GOTO/SER_NUM==0,GOTO = FORMLABELREDO
            IF_GOTO/SUB_TYPE==0,GOTO = FORMLABELREDO
            IF_GOTO/EMP_NUM==0,GOTO = FORMLABELREDO

Form opens like it should, but the info doesn't stay. I know the RED portion is where the issue is, but for the life of me I cannot figure out why.

FYI, my fellow programmer has the EXACT same code in his program and it works GREAT.

It's like there is a disconnect somewhere.


Thanks in advance.
JK

[KIRBSTER269]

I had come across this a couple of times. Where I wrote a program, created a form and it worked without any problem what so ever, Write another program, setup my form in the exact same matter, and just like you show showed up Red, and didn't stick. The only thing I can suggest was open up the form that works, and copy and paste, then if you want to make a few changes in there you can. Sorry that's all I got.

[John Kugler]

I had come across this a couple of times. Where I wrote a program, created a form and it worked without any problem what so ever, Write another program, setup my form in the exact same matter, and just like you show showed up Red, and didn't stick. The only thing I can suggest was open up the form that works, and copy and paste, then if you want to make a few changes in there you can. Sorry that's all I got.

Thanks for the assist. I've done all of that and then some. Been dealing with this all weekend, even came in on Sunday to try to figure it out. It's weird. My form that I messed with will work with a known program that works, and a form that does work in another program won't work in mine.

Frustrating.....

[KIRBSTER269]

Mine occurred in 2017R1 version, haven't tried it since then. Curious as to what version you are using that if this is an ongoing issue?

[John Kugler]

2019 r1, Build #406

[Trevor McLaughlin]

Looks like you typed your code on the wrong side of the black equal sign (=). Type TEXTSERNUM.TEXT right after the forward slash that follows PARAM. So, when you're finished you should only see one equal sign. it should look like this: PARAM/TEXTSERNUM.TEXT=SER_NUM not like you see below.

PARAM/=TEXTSERNUM.TEXT=SER_NUM

[John Kugler]

Looks like you typed your code on the wrong side of the black equal sign (=). Type TEXTSERNUM.TEXT right after the forward slash that follows PARAM. So, when you're finished you should only see one equal sign. it should look like this: PARAM/TEXTSERNUM.TEXT=SER_NUM not like you see below.

PARAM/=TEXTSERNUM.TEXT=SER_NUM

Great googlily, moogily... that was it. Great eye there, Trevor. Thanks a TON.

[Trevor McLaughlin]

No problem. I've got Forms on the brain lately since I just taught our advanced course last week. We spent a whole day on Forms!

[KIRBSTER269]

Yep, didn't even see that. Unfortunately that wasn't my case. It was just the demon being difficult with me.

[Ego Murphy]

They really could have coded it to make an obvious blank spot where you type in the name dot reference (EDITBOX1.TXT) into the field, but they didn't - they crammed the PARAM/ right next to the equal sign.

Or better yet, make a nice easy dialog box for Forms where you can simply drag-n-drop variables onto your Form items and it automatically links them.

[Trevor McLaughlin]

Ego Murphy I agree. The way this command is setup in the Edit Window is not intuitive to new users. Most programmers who are new to Forms make that mistake the first time.

When I teach this stuff, I always encourage the use of the TAB key to navigate through the Edit Window. This advances the cursor to the next editable field (Shift + Tab goes backwards). I've seen so many mistakes happen because the student simply clicks on the wrong part of a feature or command line then starts typing in the wrong spot!

I like your idea for a dialog box and dragging and dropping variables. Maybe submit that to the Idea Center. I'd vote for it, but I'm fresh out of votes!