A couple of suggestions:
The "No statetment parsed" message might occur as a result of an invalid primary key/unique index - try issuing a "alter index PK_MYTABLE rebuild" where "MYTABLE" would be your ORACLE table name. If this fails, you may have duplicate data that invalidated a unique index.
Your issue regarding the functions not linking to one reminds me of some ProIV security problems. If you are using @COMP, or you have @OPR in your ProIV file definition, you may be encountering security violations that knock you out of ProIV. Another possibility - if @COMP is set to Null/blank at the start of your function and runs through a given file, it could possibly end up with different data and thus another security error.
I'd suggest ensuring you have saved and reset @COMP at the start and end of each function, or alternatively not use @COMP in the file definition.
adilsonjMember Since 17 Sep 2003
Offline Last Active Feb 24 2006 02:46 PM
- Group Members
- Active Posts 1
- Profile Views 3,817
- Member Title Newbie
- Age Age Unknown
- Birthday Birthday Unknown
Year Started ProIV
Highest ProIV Version Used