Mary,

You are not alone. I've seen this one too when dealing with very large
recordsets, although it seemed to me that it occured when adding a workbook
while a large recordset is held in memory. You might be right about the
copyfromrecordset call being at fault though since I haven't tested it
extensively. Luckily for me, it is intermittent. In my case the first column
seems to be totally unavailable for use if I try and do anything in the
corrupted book. I typically run XP, using ADO 2.8. I can say that I don't
think it is anything to do with your use of Oracle, since I am seeing it off
a SQL db.

I don't have a solution for you, but if you find anything, please let me
know direct.

Jamie, KeepItCool, anyone else who does data stuff have any ideas or a
similar experience?

Robin Hammond
www.enhanceddatasystems.com


"Mary" wrote in message
om...
I have a vba program that, among other things, gets data from an
oracle db using ADO. I am trying to use copyFromRecorset to paste the
data into a worksheet. Everything appears to work fine (ie the data
is pasted correctly and no errors are visible). When the program is
finished and I try to add another sheet however, column A is formatted
with some unrequested combination of fill and pattern. My
program/application has been working fine for months (using oo4o to
connect to oracle) I need to change to ADO for improved performance
with the specific query used by the application and I am hoping to use
CopyFromRecordset again for improved performance. I believe I have
isolated this problem to this line (when this line is not in the
program the strange behavior does not occur).

Any help would be appreciated.

Mary