Transfering large amounts of data is one reason I am using it. But I also find it easier and quicker to set up a "template" in Excel with all my cell formatting. I do a lot of borders and shading and it would be tedious for the program to do all this stuff for each cell programmatically. The way I'm currently doing it, the program just has to dump in the data and then copy the cell formats. I guess its kind of similar to the screen designer vs. creating the screen in code debates I recall from back in FoxPro for DOS days. Its a matter of preference. I didn't always need to do more than one report at a time, but as the number of reports has accumulated, the need has now arisen. (hindsight is always 20-20). LOTS of reports may have to be re-coded.


>Why use the clipboard at all, especially since you are trying to do more than one at a time? The only thing I've ever seen recommended to use the clipboard for when automating Excel is for transferring a large amount of data because it's faster than setting each cell individually.
>
>You can just directly manipulate all of the cell properties with automation calls.
>
>>I have several FoxPro applications that are controlling Excel via OLE automation. They do a lot of copying and pasting of cell formats and such. All the copying and pasting causes a problem when 2 applications are running at the same time. It looks like they are fighting for the clipboard sometimes. One will copy to the clipboard, then before it can paste, another one copies over what was on the clipboard. Is there any way I can make them politely wait for their turn, or a way to use multiple clipboards?