Skip to main content

I have a legacy Extra macro which has Fx keys defined with: 

Sess0.Screen.Sendkeys("<PF8>")

Should it really be:

Sess0.Screen.Sendkeys("<F8>")

Will the first assignment cause an error?

Thanks


#Reflection

I have a legacy Extra macro which has Fx keys defined with: 

Sess0.Screen.Sendkeys("<PF8>")

Should it really be:

Sess0.Screen.Sendkeys("<F8>")

Will the first assignment cause an error?

Thanks


#Reflection

Hello jcbolton,

You want to use the first line of your example.  Refer to the Extra! API documentation for all of the Mnemonics for the 3270 Function Keys.

 

Best Regards,

Jeff


Hello jcbolton,

You want to use the first line of your example.  Refer to the Extra! API documentation for all of the Mnemonics for the 3270 Function Keys.

 

Best Regards,

Jeff

Thank you for your response.

I'm attempting to find where my macro is failing.  When the error says "Type mismatch occurred at line: xxx", does the xxx count include comments and blank lines?

Thanks.


Thank you for your response.

I'm attempting to find where my macro is failing.  When the error says "Type mismatch occurred at line: xxx", does the xxx count include comments and blank lines?

Thanks.

The comments are not counted in the compiled code.  So the comments would not count in your error.

Thanks,

Jeff

 


The comments are not counted in the compiled code.  So the comments would not count in your error.

Thanks,

Jeff

 

Thank you again for your response.

I hate to be a pest, but how about the blank lines?  Are they counted?

Thanks,

John


Thank you again for your response.

I hate to be a pest, but how about the blank lines?  Are they counted?

Thanks,

John

I don't believe the blank lines are counted either.  Try creating a line that you know is bad code, a reference to an object or variable that is undefined in your code.  Maybe put a comment in line one, a blank line in line two and a bad reference in line three and see where what line the error is reported in your code.  Please report back with the results so we will have an answer posted in the forum.

Thanks,

Jeff

 


I don't believe the blank lines are counted either.  Try creating a line that you know is bad code, a reference to an object or variable that is undefined in your code.  Maybe put a comment in line one, a blank line in line two and a bad reference in line three and see where what line the error is reported in your code.  Please report back with the results so we will have an answer posted in the forum.

Thanks,

Jeff

 

jcbolton,

I was able to test this with the macro editor using a legacy Extra! Basic Macro Editor.  I find that the line number you see in the editor is the same as the line number that is being reported in the error message.

Capture.JPG

So in the example above I have a reference to a bad object in line 11 and when I run the macro, I do see an error in the line where I attempt to reference the bad object.

Capture.JPG

Regards,

Jeff