A long performing workbook suddenly developed this strange problem. I was unable to paste into any Table cell (Table 1). The Copy function loaded a selection into the Paste buffer. Pasting functioned everywhere except within my table.

I was able to recover by copying the data from Table1 onto a scratch worksheet, converting that range into a new table. I checked to verify that the paste function worked on this new table. I then copied this new table back to a new location on Table 1's worksheet thus creating a second table on that worksheet. I checked the paste function again. It worked. But to my surprise, the paste function now also worked on Table 1 !

However, the experience has left me rattled. I would be interested to hear if anyone else has encountered this problem. I code VBA macros extensively and would like to know if I could check into the table or worksheet properties to find some clue as to what had gone wrong.

Thank you

On 1/25/2018 4:29 PM, Desmond Walsh wrote:
A long performing workbook suddenly developed this strange problem. I was unable to paste into any Table cell (Table 1). The Copy function loaded a selection into the Paste buffer. Pasting functioned everywhere except within my table.

I was able to recover by copying the data from Table1 onto a scratch worksheet, converting that range into a new table. I checked to verify that the paste function worked on this new table. I then copied this new table back to a new location on Table 1's worksheet thus creating a second table on that worksheet. I checked the paste function again. It worked. But to my surprise, the paste function now also worked on Table 1 !

However, the experience has left me rattled. I would be interested to hear if anyone else has encountered this problem. I code VBA macros extensively and would like to know if I could check into the table or worksheet properties to find some clue as to what had gone wrong.

Which release/OS and are patches/updates current?

I just recently upgraded to Office 2016 and it is _much_ less stable
than old version--it's been quite easy to crash it for no apparent cause.

macro coding errors while debugging are especially good at doing the
dirty it seems I have noted. In fact, I spent the entirety of yesterday
afternoon trying to recover from a repetitive cycle of crash/restart/fix
-macro-typo/close-debug-window retriggering crash/restart/fix...

I am _not_ impressed nor pleased; I'm seriously considering seeing if
can reinstall 2010.

--

On 1/25/2018 4:29 PM, Desmond Walsh wrote:
A long performing workbook suddenly developed this strange problem. I was
unable to paste into any Table cell (Table 1). The Copy function loaded a
selection into the Paste buffer. Pasting functioned everywhere except
within my table.

I was able to recover by copying the data from Table1 onto a scratch
worksheet, converting that range into a new table. I checked to verify that
the paste function worked on this new table. I then copied this new table
back to a new location on Table 1's worksheet thus creating a second table
on that worksheet. I checked the paste function again. It worked. But to my
surprise, the paste function now also worked on Table 1 !

However, the experience has left me rattled. I would be interested to hear
if anyone else has encountered this problem. I code VBA macros extensively
and would like to know if I could check into the table or worksheet
properties to find some clue as to what had gone wrong.

Which release/OS and are patches/updates current?

I just recently upgraded to Office 2016 and it is _much_ less stable than old
version--it's been quite easy to crash it for no apparent cause.

macro coding errors while debugging are especially good at doing the dirty it
seems I have noted. In fact, I spent the entirety of yesterday afternoon
trying to recover from a repetitive cycle of crash/restart/fix
-macro-typo/close-debug-window retriggering crash/restart/fix...

I am _not_ impressed nor pleased; I'm seriously considering seeing if can
reinstall 2010.

Why did you replace 2010? Makes sense to keep the old version until you get a
chance to play with the new one; then remove whichever one you don't want to
keep later!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

On 1/26/2018 8:01 PM, GS wrote:
....

Why did you replace 2010? Makes sense to keep the old version until you
get a chance to play with the new one; then remove whichever one you
don't want to keep later!

Old machine died; went ahead and "upgraded" when replaced it...

--

On 1/26/2018 8:01 PM, GS wrote:
...

Why did you replace 2010? Makes sense to keep the old version until you get
a chance to play with the new one; then remove whichever one you don't want
to keep later!

Old machine died; went ahead and "upgraded" when replaced it...

Do you still have 2010?

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

On 1/27/2018 3:25 PM, GS wrote:
On 1/26/2018 8:01 PM, GS wrote:
...

Why did you replace 2010? Makes sense to keep the old version until
you get a chance to play with the new one; then remove whichever one
you don't want to keep later!

Old machine died; went ahead and "upgraded" when replaced it...

Do you still have 2010?

Yes, altho I've not dug the CDs out and I no longer recall otomh whether
they were tied to the machine or whether I have the necessary license
key to install on this one...

--

On Sat, 27 Jan 2018 08:47:27 -0600, dpb wrote:

Old machine died; went ahead and "upgraded" when replaced it...

"updated" < "upgraded"