Yes.

In fact I just went back to look at my original and the modified version is actually there.

I guess there's a small "hole" in the logic controlling "Update". No big deal, overall.

Cheers

>The UT has been a little flaky lately - I know Michel's been making a lot of changes.
>
>>Yea,
>>
>>I had a mental block (happening more often) and I thought I had updated this message to say 'forget about it' but you seem to have gotten there first so my update didn't take (without indication that it didn't).
>>
>>Thanks anyway.
>>
>>
>>>Jim,
>>>
>>>Imagine a PRG file called TheProgramFile which is a "library" of small functions and procedures.
>>>As you know, you would SET PROCEDURE TO TheProgramFile ADDITIVE in your Main program to use such a program library.
>>>
>>>Now imagine that the functions/procedures included in it contain one called TheProgramWhichDoesAddition and one called TheProgramWhichDoesSubtraction.
>>>
>>>You would say DO TheProgramWhichDoesAddition IN TheProgramFile.PRG or DO "TheProgramWhichDoesAddition" IN TheProgramFile.
>>>
>>>
>>>>The following is extracted from the VFP7 documentation under "Function command - Parameters" in the latest MSDN library.
>>>>
>>>>Does anyone know what it means?
>>>>
>>>>---- start of extract
>>>>FunctionName
>>>>In Visual FoxPro, function names can be up to 254 characters long.
>>>>
>>>>To distinguish a program file name with more than 10 characters from a function beginning with the same 10 characters in these two products, surround the program file name with quotation marks or include an extension after the program file name.
>>>>---- end of extract
>>>>
>>>>I don't know if this was also present in VFP6 documentation (overlaid by VFP7).
>>>>
>>>>Thanks
>>>>JimN