At 09:09 PM 03-08-01 -0700, you wrote:

>The problem is: The user requires that the MasterLink field , which is
>ACCOUNT always be displayed in UPPER case. And the actual database field
>is in *lower* case. It is very convenient to use the CharCase Field
>Property to UPPER case it for display.
>
>But if I do that, the MasterLink Param is also passed in UPPER case rather
>than in the *actual* case of the field in the database. And therefore, no
>matches.
>
>Can anyone suggest some simple solutions?

Phil,
You are being confronted with what can happen when you use non-atomic keys. Without going into one of my famous sermons :), any column that could be affected by a user's requirements should *NOT* be a key.

If possible, add a new, atomic column to both tables, an integer or INT64 that becomes the primary key of the master table and the foreign key on the detail table. Then you can display the account number in whatever what you like and, in fact, you will do yourself a favour for search purposes by adding a trigger-populated proxy column that contains the account code uppercased.

Regards,
Helen

All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________