So, there's been word floating around that there is an unofficial syntax checking tool that one or more people have that allows you to see if your WF7.x code will work in WF8.x. Does anyone know about this tool, and where one could get his hands on a copy of such?

I'm currently dealing with a procedure that continues to give me the 32027 hard kill error or fails to run but never gives me an adequate error to work with despite my efforts to place -EXITs throughout the .fex, add -SET &ECHO = 'ALL', or even set XRETRIEVAL = OFF in my tracing. It is VERY aggravating! Does anyone else know of any other tricks that may help to troubleshoot a procedure that I haven't already tried? That, and know where I could go to get me a copy of this "tool" if it exists?

Thanks in advance!

This message has been edited. Last edited by: CoolGuy,

I think everyone would be interested.

Waz,

I bet.

All,

IBI really needs to focus on documenting things completely and correctly (proof: lacking documentation referenced in this discussion), fix the poor search they have implemented for their online docs, and provide adequate troubleshooting methods and messaging for existent functionality, while pausing on the product releases. This is pretty bad.

The issue with my procedure was that there were incorrectly applied actual and usage data types for a specific field in the new environment where the old one had something different for them. Made the corrections and it now works.

About a year ago we had this done and I had to zip up our source code and send it to IBI for them to scan. They, in turn, will provide a high-level listing of SET’s, INCLUDE’s, HTML compatibility issues, Syntax Warnings, etc.

CoolGuy,

quote:

The issue with my procedure was...

Would you please be so kind as to post the incorrect and correct formats which caused this issue.

Thanks, Doug

Doug,

Old environment - Actual: I4  Usage:  I11

New environment - Actual: P20  Usage:  P10  (It may have been P10 then P20.  Can't remember.  Sorry.)