>OK, Tiger, so it only happens in VFP 3.0b & not 3.0?

No, it happened in both. I got it fixed now, but I don't know why. I am trying to read lines in files that are about 355 chars long. When I had
first developed this, I was getting really strange errors when I tried to read these lines using FGETS(). (corrupt object files, etc) So, I figured it was a limitation with VFP not being able to read over 255 chars(yes I specified the correct length in the function call). Then I used a DLL to do this, and it worked fine.

This time, I only needed about half of the lines, so I changed the calls to the appropriate FoxPro function, and the same thing happened. It wasn't the DLL after all, but an attempt to read a line over 255 chars long. I'm really confused. Does VFP have a string length limit? Maybe that is it, but it is still working in my CS app, with a DLL shoving the 355 char string into a memvar.

At any rate, it is working now, after I applied a couple of "hack" fixes. This is a temporary thing, but I am worried about my existsing app....

Thanks,
Scot.