Sergey,

Their res was 1024 * 768. Interestingly, I'd borrowed a larger monitor and had altered mine. Now back with my old monitor I've put mine back but I still don't get the errors like they do. I followed Naomi's advice and didn't get the same errors but got different ones on exit.

Thanks

Terry

I have a GP error routine hat gives most info on the error (MESSAGE(), PROGRAM(), etc); What sort of extra info were you thinking of my getting with AERROR()?

>What's desktop resolution on users PCs? Did you use AERROR() to get additional info about the error?
>
>>It never rains but it pours. As you may have noticed from recent post, I'm pretty new to this Excel automation lark. However, I do have some code that's been working fine for me. I've built my exe and it works fine as well as from VFP -on MY m/c
>>
>>Now when my users invoke the exe and run this code:
>>
>>

>>EXPORT TO &lcFilePath TYPE XL5
>>loExcel = CREATEOBJECT([Excel.Application])
>>With loExcel
>>  .Workbooks.Open( lcFilePath)
>>  If not thisform.lCustom		&& If chose non-custom, formatted o/p (default)
>>    With .ActiveWindow
>>      .DisplayZeros	= .F.
>>      .Width		= 1124       && <---------------- THIS THE OFFENDING LINE
>>      .Height 	= 645
>>   EndWith
>>  With .ActiveSheet
>>    ...
>>

>>
>>my error routine reports:
>>
>>OLE dispatch error 1479 at line 30 of ...., line of code = .
>>
>>The actual line is:
>>
>> .Width = 1124
>>
>>but the routine says "."
>>
>>What gives here?????
>>
>>Of course Help tells me zip.
>>
>>I suspected that it might be because Excel was already open on their m/cs, so closed it, but no difference.
>>
>>'ppreciate it.