Be careful with this. I've had LOTS of problems with long file names and macro expansion. In all cases, using ( ) fixes the problem. Instead of:

&var

I use (var)


>>I use the following statement in a form. ItemNumbers is an edit box. It has been serving its purpose quite neatly until now.
>>
>>=STRTOFILE(THISFORM.OrderPageFrame.Page2.ItemNumbers.Value,'items.txt')
>>
>>I spent the last hour observing it fail. I have isolated the issue to this specific statement as I can view from Windows Explorer the items.txt file. Interestingly, this statement only works once for this form. When it is executed again, the items.txt file is not created.
>>
>>I have been banging my head trying to figure this out. Finally, I ran the exact same app on a different machine. It worked!
>>
>>The app that choked on this was running on a Win2000 machine. The app that ran this fine is on a Win98 machine.
>>
>>Any suggestions?
>
>I have noticed occasions, on my W2K box, when fully qualified object names do not work as parameters to functions or procedures. So, I assign the object's value to a variable and use &var as the parameter. Usually solves the problem.
>
>JLK