>It works when I store a .prg's contents in it that are up to 128 lines so far. Actually, since we only use FPD26 and VFP7/VFP8 I should be okay as far as the versions go. I have the Hacker's Guide at home so I cannot check it here at work. What is the limit of FPUT? Do you know off the top of your head? During testing, I was reading the memo field line by line and writing it to the .prg file that way, but then when I tested it reading it all in at once and writing it all at once, it worked so I changed it. Guess I'll change it back to be safe.
>
>Tracy
>
If you would see how many windows I already had open, you would not ask me to check Hacker's Guide :))

Anyway,
=====================================
If you'll be writing out a text file, consider SET ALTERNATE and SET TEXTMERGE as well as using LLFFs.

But for hacking binary formatted data, there's nothing better than the low-level file functions. Let's see what they can do.

FPUTS() writes data to an opened low-level file. FPUTS writes characters until it reaches the smaller of these two limits: the number specified in the third parameter, or the total length of the string supplied.

Usage nRetVal = FPUTS( nFileHandle, cString [, nBytes ] )

(Don't see any reference on limit)

FWRITE() writes data to a low-level file. Unlike FPUTS(), FWRITE() writes exactly what you specify, without appending any characters (such as carriage returns or line feeds). Use FWRITE() when you are trying to write data out to a very specific file format, such as Windows CardFile, FOXPRO.INT or another binary format.

Usage nRetVal = FWRITE( nFileHandle, cString [, nBytes ] )

=================================================
So, there are no mentioning of any limits, though I'm sure, there are some. (Probably in VFP help then)

Nothing in VFP help either