>>I'm working on an existing app with 65+ views, adding some multi-language capabilities. No problem with character fields, I have a function that checks the right language and does a lookup in the translation table. I just replace the original character field with a calculated field with the same name and length containing the translated character string.
>>
>>However there are several dozen memo fields, most with a page or more of data. Is there any way to force the calculated field in a view to become a memo field? I can change the view but the result must have the same field names and field types as the original since I can't change the application itself.
>>
>>I have rather klutzy workaround involving a table with blank memo fields in a single record. The view is designed using this table. When loading the application I make a cursor with the same name and field names containing the translation information. But I really dislike having tables and cursors with the same name!
>>
>>Any suggestions? Better workarounds? Keep in mind that I have to work within the existing views. I can't add any code after the view is opened to update the memo fields.
>>
>>Thanks!
>>Barbara
>
>First of all, welcome back! Haven't seen you here for a while.
>
>For VFP9 you can use CAST() function. In prior versions you need to have an extra table (cursor) with one blank record and a memo field to add to your query.

Thanks, Naomi. Unfortunately I'm stuck with VFP8 so CAST() isn't in the cards. I guess I'll have to go with the klutzy method I've worked out.