Man, today has been one brick wall after another.

I'm working on some DBA security, and I want to use DB_INFILE. In my source synonym, I have a defined field as ME/A150 = UPPER(CNCTUSR('A150')).

In a separate file, I have a field called USERNAME that is an actual field in the table (not a DEFINE).

So, my DB_INFILE says (the_other_file, ME, USER_FIELD).

I keep getting strange error
END
0 ERROR AT OR NEAR LINE 1 IN PROCEDURE Account_ListFOCEXEC *
(FOC32499) INVALID USE OF FIELD NAME IN DB_LOOKUP/DB_INFILE: USER_FIELD
(FOC009) INCOMPLETE REQUEST STATEMENT
BYPASSING TO END OF COMMAND

Has anyone seen this?

This message has been edited. Last edited by: <Emily McAllister>,

quote:

(FOC32499) INVALID USE OF FIELD NAME IN DB_LOOKUP/DB_INFILE: %1
Only real fields in the lookup Master File are valid as lookup and return fields.

I don't think this will be of any help, but perhaps modifying the DEFINE will correct the problem:

ME/A150 WITH CNCTUSR = UPPER(CNCTUSR('A150')).

Or, shouldn't DB_INFILE be referencing USERNAME?

DB_INFILE says (the_other_file, ME, USERNAME)