This content has been marked as final. Show 6 replies
The idea of joining a VARCHAR2 to a NUMBER is a little bit scary to me. I would change the REPORTER_INFO.REPORTER_ID to VARCHAR2(10) and create a PK-FK relationship in the database, but...
If the current relationship (below) is working, I would leave it alone.
You could then change your REPORTER_HISTORY block's "Where Clause" in the property palette to
call_queue.participant_id = reporter_history.reporter_id
I would think that would work for you.
Nope...this didn't work. When the Master record is a Prospect (which can have characters in the value) the relation still fails with:
In the Detail block's Default Where property I tried adding this where condition, but I'm still getting the error message:
FRM-40356: Invalid number in example record. Query not issued.
Any other thoughts on working around this issue would be greatly appreciated.
a.participant_type = '001'
I tried the suggested solution, but it didn't work.
I was afraid of that since you were mixing NUMBER with VARCHAR2. If you are not allowed to update the REPORTER_HISTORY.REPORTER_ID column from NUMBER to VARCHAR2, then I would create a view with the same columns as REPORTER_HISTORY but convert the REPORTER_ID to VARCHAR2 and reference that in the form module instead of the table.1 person found this helpful
So... if the REPORTER_HISTORY has a layout of:
Then I would create a view based on that table:
REPORTER_ID NUMBER(8) REPORT_TEXT VARCHAR2(200) etc...
I would then modify the form module to reference the view instead of the table. The join should work without any problems since you will now be joining VARCHAR2 to VARCHAR2.
create or replace view REPORTER_HISTORY_VW as select to_char(reporter_id) reporter_id, report_text, ....
That sounds like a good idea. I'll give that a shot.
Also, I think the error is not critical and could be suppressed without harm since no records would be retrieved even if the data types did match as Char.
Thanks so much.