>Yes, my job is like a hobby. I use to complain in Egghead stores about them selling dBASE IV and not FoxPro 2.x. I was once blown away in 1992 when I had only went to 2 FoxPro user groups and only knew about 10 FoxPro programmers, and Tom Rettig told me about this idea of a INDEXSEEK() function that would seek a record but not move the record pointer, and that he said he was going to call Dave Fulton about having it added to FoxPro 2.x. I was amazed that he could just call up and ask for a new function to be added. Now that I'm on the VFP team, it's a dream to be able to think up useful additions to VFP and have them added like STRTOFILE(), FILETOSTR(), ALINES(), VARTYPE(), etc. I sometimes feel like Charlie in the movie "Willie Wonka and the Chocolate Factory" where I work on making Visual FoxPro instead of chocolate. I remember the line from that movie "We are the dream makers, and we are the dreamers of our dreams."


Ken,

Hopefully you don't mind me butting in here, but since you mentioned you came up with the idea of FILETOSTR()......

I am doing some work with EDI. I noticed FILETOSTR() and thought it would be a great idea to use it to import the EDI text file. Examples I saw used MEMLINES() to determine how large the variable initialized by FILETOSTR() is. But MEMLINES() ran for 10 minutes or so, due to the size of the file.

I set up my code to assume that there are no blank records, so I test for EMPTY() to determine when I'm at the end of the FILETOSTR() variable. Does this sound alright to you, or do you have a better idea for scanning through the variable.

Thanks,

Pf