Yep, I surely think it was because now that I am doing things in their proper order and am cleaning up after using Excel, things are now working properly. You know, there is a lot to think about when you mess around with Office Automation.

Hey, you are in my home state. Are you a native Texan? I used to live in Round Rock, north of Austin a bit, maybe 20 miles north.

I was exiled to California (USSR fo Kalifornia) years ago and have been here most of my adult life, due to the miltiary, aerospace, and FoxPro consulting. But, the glory days out here are all gone. There are no available FoxPro jobs out here these days except at CountryWide Home Loans (Bank of America owns it now) every now and then.

My DICE job alerts show very little activity in Texas and none in any other parts of the western Untied States. That is not a good sign.

I feel kind of dumb right now feeling that I should have gotten busy three years ago, or more, with .NET. But, ce la vie. At age 56, not many companies want to hire me, due to my advanced age, although I know I still look about age 25. (Ha! in my dreams only.)

Anyway, thank you for responding to this psoting, Frank.

Cecil

>Cecil,

>It's most likely that one of those Excel sessions was still attached to your file. While playing with Excel automation tasks you need to make sure you clean up especially while you are actively debugging code. You should make an explicit oExcel.Quit() call before you clear your reference to the object.

>>Before I put in the RELEASE command to RELEASE oExcel, oWorkBook, a bunch of the EXCEL.EXE processes were piling up (threads of them) in the Task Manager (or stack) and were never closed; I figured this out later when I opened Task manager, and then killed every one of the EXCEL processes, shut down my machine and did a cold boot.