Hi Sharon,

Although, I'm not using Excel, I do believe something like this is occuring. It would be nice if there was a way of detecting that FoxPro is still busy and preventing any further code from executing until it is done. I had always thought that FoxPro code was synchronous but it seems that rarely it behaves as if it is asynchronous.

>Re: the unusual 1705 error

>I've have an error like this when working with excel automation. The problem turned out to be that the code filling in the spreadsheet wasn't done when the fox code tried to close excel. Basically it wasn't done with it's previous number crunching when it went on with the program. Sometimes the computer would finish crunching numbers faster and I wouldn't get the error, sometimes it wouldn't finish and then would blow up. Putting in wait windows so it would finish helped diagnose this is what was going on, but wasn't a good solution to the problem because every user's computer functions at a different speed. You'd never know how long to wait. I didn't really solve the problem at all, I changed the way excel was doing the calculations to something faster. But I thought it might give you some insight if something like this is what could be occuring with you.
>
>Sharon