date format as a key field

[gacampb]

Have a primary business object (transaction broker) with a date format field as one of the keys (not the first key). Also have a text business object that has a text relationship to the primary BO. I can not get the “O” user exit program to compile. Telling me the types do not match. Any info would be helpful.

[jdiggs]

Can you post the offending code? I've had a couple of incidents that may be related.

[gacampb]

Here is the code from the user exit that gives the errors:

C eval pSQLStmt='DELETE FROM PU292F'
C + ' WHERE '
C + 'KVNDNR = '
C + %trimr(getQuoted(mKEY001))
C + ' AND '
C + 'KITNBR = '
C + %trimr(getQuoted(mKEY002))
C + ' AND '
C + 'KHOUSE = '
C + %trimr(getQuoted(mKEY003))
C + ' AND '
C + 'KEFFDT = '
C + %trimr(getQuoted(%char(mKEY004)))
c eval *in90=ExecSQL(pSqlStmt)
C*
C zDeleteText ENDSR

the error is : RNF0386 30 1284 001274 The first parameter for %CHAR is not valid.

The key field date is defined in the program like this:
D* Effective Date
D mKEY004 00010A
D cKEY004 00010A

In the BO the attribute is defined as a date type. If the relationship is removed the code compiles but when the text BO is setup with the relationship the error occures.

[jdiggs]

That's a good one. It seems like for some reason the key004 definitions may not have been updated after an initial assignment to a 10A field. Have you done all of the obvious things like checking the key sequence in the BO, re-generating, and re-compiling? I'm sure you have, so I guess you'll let us know how this turns out once Infor fixes it?

[HenrikW]

We had the same problem, and got a fix in a new Power Link level, i don't remember what level, but relatively new.

What release and fix level are you at?

We are now at R7.7 on PL level 40.76 and planning to upgrade to 40.82 very soon.