#39 R2.5.0b Language errors

R2.5.0
closed-fixed
3
2003-09-04
2003-08-27
Jorg Janke
No

In Release 2.5.0b, the Application Dictionary definition of
the table AD_Language is "messed up" with the
consequence, that you cannot add/change languages.

You may get errors like ORA-00933: SQL command not
properly ended

Here the manual fix:
(Note that the table AD_Language is somewhat non-
standard)
- With the Administor role, go to Window Table & Column
- Navigate to table AD_Language
- In the Tab "Column" change the entries:
-- AD_Language is the Key(!) not Parent
-- AD_Language_ID is NOT a Key Column nor Parent and
needs to have a default = e.g. (@SQL=SELECT NVL(MAX
(AD_Language_ID),0)+1 AS DefaultValue FROM
AD_Language)

Save. You then can add/change any languages again.

Discussion

  • Jorg Janke

    Jorg Janke - 2003-08-27
    • priority: 5 --> 3
     
  • Jorg Janke

    Jorg Janke - 2003-09-04
    • status: open --> closed-fixed
     
  • Carlos Olink

    Carlos Olink - 2003-09-18

    Logged In: YES
    user_id=835558

    Hello Jorg, I have a question about this patch:

    What I understood:

    change FROM:
    -- AD_Language is the Key(!) not Parent

    TO:
    -- AD_Language_ID is NOT a Key Column nor Parent

    what about the next step, where should I write that?

    and needs to have a default = e.g. (@SQL=SELECT NVL(MAX
    (AD_Language_ID),0)+1 AS DefaultValue FROM
    AD_Language)

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks