I quickly reviewed the code in the Calvin's article and I see now that the problem is not with fread and fwrite but with the array. In VFP9 arrays are only limited with the available memory.

Now, since the array solution doesn't work, you simply may switch to the cursor solution or something similar.

>I wondered about this limitation on the FREAD() and FWRITE(), but I guess what is confusing me so much is the fact that the code worked with a 10MB EXE, which would also put these numbers far above the limits too. I have tried to understand the code but I guess I just don't know enough about the low-level file structure of tne EXE to see where the manifest should be written and what "other" sections of the EXE need to be added back to the end of the file.
>
>I have not found very much evidence that the majority of VFP developers are even adding a manifest to their EXEs. It seems like this should be something that is talked about widely in the VFP community since Vista seems to be here to stay.
>
>
>
>>>I have been using the code from Calvin Hsia's weblog (http://blogs.msdn.com/calvin_hsia/archive/2007/04/13/add-a-manifest-to-control-your-application-vista-uac-behavior.aspx) to add a manifest to my VFP exe for several months with great success. The size of my exe has now increased to 17+ megabytes and now I am unable to use you code to create a manifest. It is crashing on the line asec[i]=FREAD(h,sz) with the error "function argument value, type, or count is invalid". At the time of crash, i=1, h=37, and sz=17,779,509. Any advice?
>>
>>The FREAD() and FWRITE() functions are limited to 65,535 bytes. You can create your own UDF() that can read write longer strings or use Windows API functions.