run-time error 4605 when using a macros in excel 2010 (windows 7)

**rpt21** · 07-12-2011, 08:04 PM

The following macros (which was created with the help of this forum-thanks) is used to transfer data from excel to several tables within a word document:

Please Login or Register  to view this content.

I recieve a an error message saying:

"run-time error 4605

This method or property is not available because the clipboard is empty or not available"

Stepping into debugger it stops here: "wdApp.Selection.Paste"

This code works fine in both excel 2007 and 2010 in XP mode, but is much slower. It seems to only fail in windows 7? It also seems to fail at different points, cutting and pasting into some of the tables then failing.

Please could you help me determine what is wrong.

Much appreciated,

rpt21

**MarvinP** · 07-12-2011, 08:14 PM

Hi rpt21,

I first believe the error message. Lets go with the clipboard is empty. That would mean that what you thought you copied wasn't there. Looking at the code it refers to a Table(T) and I assume T is a number. If you were refering to table 5 or Table(5) and there was no table 5 in the workbook or document you could easily get this message.

When it stops next time and you go into the debugger, hover you mouse over the T in Table(T) to see what value it is. Then go to where it is supposed to be pulling the copy from and see if there is really one of those there.

**rpt21** · 07-13-2011, 03:59 PM

Hello MarvinP,

There is definitely a table where is should paste, the document is made up identical pages and each page has five tables in it. The data is pasted into every 5th table since the other tables contain other content.

The macros fails at different points, so it is not one table that is problematic.

This code has worked for a while, it is only since I have upgraded to Windows 7. As I mentioned, it works on my virtual XP but it is annoying to use this each time I need to run this macros.

regards,

Ross

**MarvinP** · 07-13-2011, 05:47 PM

Hi rpt21,

Because it fails at different times and places, I'm thinking some well placed Application.DoEvents might solve the problem.

Search for VBA DoEvents or look at
http://en.allexperts.com/q/Visual-Ba...s-Function.htm

**Imardin** · 05-04-2012, 12:02 PM

It's been a while, so you may have solved this already, but in case anyone else has a similar problem:

I started getting this error when I upgraded from MS Office 2003 to 2010, but the macro still worked perfectly well in 2003.

The tables were there, but I noticed that sometimes the copying didn't work. As this didn't ever happen in debug mode, I added 5 secs waiting time right before the copying.

This makes the macro slower, but as it takes a few minutes to run anyway, I didn't mind.

Please Login or Register  to view this content.

**junino78** · 01-26-2015, 12:44 PM

Hey !

Thanks you for the previous solutions!

**FDibbins** · 01-26-2015, 12:49 PM

junino78 welcome to the forum

Unfortunately your post does not comply with Rule 2 of our Forum RULES. Do not post a question in the thread of another member -- start your own thread.

If you feel an existing thread is particularly relevant to your need, provide a link to the other thread in your new thread.

Old threads are often only monitored by the original participants. New threads not only open you up to all possible participants again, they typically get faster response, too.