Well, I did that, and lo and behold, it's telling me that the excel file format is invalid (error 1661). This makes no sense at all. It works for me on the same excel file (the file is on the network, and we both point to it). Also, when he types the line manually into 'x-ray' (the command window type program), the excel file loads very nicely.

This is way bizarre. We both have the same excel odbc driver and the same installation of excel. I have full vfp9 and he has vfp9 runtimes.

Any thoughts? I'm baffled.


>Add STRTOFILE() to your ON ERROR routine and record the error code and message to a file. Maybe it'll give you idea what the problem is.
>
>>Wish I knew. I have an on error trap set up for the 'append' line. If it errors, I put out the message that it couldn't load. I know the table is open; I know the xl file exists and is available (I use the full path to the file). As I said, when I run it, it works properly. When he runs it, it errors out with my error message, and the table remains empty.
>>
>>I brought the code home and ran it here and had the same issue with it erroring out on my own pc. I just looked at the code I posted and it is not quite the same as in the compiled program. In the compiled code, it is:
>>
>>

Append from (lcClaimFile) type xl5 sheet "loss_run"

>>Here at home, when I remove the quote marks from loss_run it works. For whatever reason though, at work, on my computer, the quote marks did not cause any problem. Tomorrow, I'll remove them, recompile and see if it fixes the problem on his system (and, of course, doesn't cause an error on mine).
>>
>>