Comments on: Catching Paste Operations

By: calidor

calidor — Wed, 29 Sep 2010 11:11:00 +0000

This workbook..
' Activate/deactivate - we only want to capture ctrl+v on this specific workbook
Private Sub Workbook_Activate()
Application.OnKey "^v", "RunMyPaste"
End Sub

Private Sub Workbook_Deactivate()
Application.OnKey "^v"
End Sub

Public Sub RunMyPaste()

' worksheet is unprotected for VBA, if cell is locked - do not paste (VBA would allow it)
If ActiveCell.Locked = True Then
Exit Sub
End If

Dim DataObj As New MSForms.DataObject
Dim S As String
DataObj.GetFromClipboard

' Set up for error checking
On Error Resume Next
S = DataObj.GetText

' Clean non-printable characters
S = Application.WorksheetFunction.Clean(S)

' Check if error and check if zero length (blank)
If (Err.Number 0) Or (Len(S) = 0) Then
On Error GoTo 0
Exit Sub
End If

'Paste
Application.EnableEvents = False
Application.ScreenUpdating = False
'backup cell value
Dim sValue As String

sValue = ActiveCell.Formula
ActiveCell.Formula = S

If ActiveCell.Validation.Value = False Then
'Give error message
MsgBox ActiveCell.Validation.ErrorMessage, vbCritical, ActiveCell.Validation.ErrorTitle
ActiveCell.Value = sValue
Application.EnableEvents = True
Application.ScreenUpdating = True
Exit Sub
End If
Application.EnableEvents = True
Application.ScreenUpdating = True

' paste value again so worksheet_change is processed (colors etc)
ActiveCell.Formula = S
End Sub

By: Helen Ellwood

Helen Ellwood — Thu, 25 Feb 2010 11:46:00 +0000

This code looks perfect for what I need it for, but the link to http://www.savefile.com/files/1398313 doesn't work!

Bjørnar Tofteland, are you still out there? And is there anywhere else I can get a copy of this code?

By: Peter Clough

Peter Clough — Wed, 30 Apr 2008 22:39:00 +0000

Some thoughts (no code) borrowed from an approach I took to this problem. First, before the workbook is saved, it hides all sheets except a warning sheet which explains that macros must be enabled to view the meaningful sheets. Second, all sheets are PW protected and all the fields are locked except data entry cells. Third, Most editing is done in VBA, so there is little data validation. Finally, whenever there is a change in a data entry cell, the entry is edited, reset to a non-harmful state if in error, and formats, conditional formats, and validation if any is reapplied from a mask on a hidden sheet, customized to that particular cell or range. This has multiple advantages: the user can’t screw up formats or edits (we all do it, usually by inadvertence), 1000 cells never go to div0 or NA or NAME? and force you to debug, it allows paste operations into data entry cells, and it’s relatively secure.

By: Bjørnar Tofteland

Bjørnar Tofteland — Sat, 23 Feb 2008 16:14:00 +0000

I have used the feedback from jkpieterse and Alistair to modify my project. I have now created a class module to take care of the preserving of datavalidation and formatting.
You can still do as much cut, copy, paste and drag/drop as you like.
The one level undo works for multiple input ranges.
I have also added a couple of UDF's that I use for all references to the input area, so no references gets destroyed when you cut or drag/drop on cells in the input area.
Inserting cells is prevented by worksheet protection.
For those of you who wants to take a look at this I have made a demo, available from the link below.
This demonsrates the use of this class module on 2 separate input ranges. There is also a output range showing the use of the UDF's that references the input areas. Try cut/paste and you can see that no references is destroyed.
The use of a template row for all validation and formatting, that Alistair suggested, also makes changes easier, I dont have to copy the changes to all rows, just change the template.
If the user that puts in the data don't activate the macro's, he can still use the workbook, and can probably destroy some formatting and validation. But the template cells is hidden and all invalid data is highlighted and can be corrected, when you reopen the workbook with macros activated.

http://www.savefile.com/files/1398313

By: Bjørnar Tofteland

Bjørnar Tofteland — Tue, 22 Jan 2008 06:48:00 +0000

Thanks JK. I tested the Application.OnUndo as my last code and it works perfect.

By: jkpieterse

jkpieterse — Mon, 21 Jan 2008 10:03:00 +0000

Forgot to add that the Application.OnUndo must be the last entry of your code.

By: jkpieterse

jkpieterse — Mon, 21 Jan 2008 10:02:00 +0000

AFAIK if you set the APplication.OnUndo, the button will be enabled, but the hsitory will be limited to one entry: the one you just defined in your code. Indeed the history is wiped by your code.

Check out this page for an example on building the undo:
http://www.jkp-ads.com/Articles/UndoWithVBA00.asp

By: Bjørnar Tofteland

Bjørnar Tofteland — Thu, 17 Jan 2008 19:33:00 +0000

Thanks for all your feedback.

I have not had any time too figure out the undo button yet. At first I also tought that the Application.OnUndo would be a easy solution, but I think Alistair is right about that the button will be disabled, when I actually need it.
The tip about only copying one row is a good tip, and I think I will try to do this. That way I will also be sure that all rows have the same validation and formatting, in case I manage to destroy some of this myself when I make changes to the sheet (with restore function disabled). I then only have to edit and test the first row.
As Alistair mentioned, I have also noticed that the fill handle (the little black + in bottom right corner) in a cell with drop down list is sometimes difficult to reach because of the drop down arrow beeing on top of it.

I'm also going to use this solution in another Workbook where cells in other sheets will have references to the input range. I see that this could bring up some problems, as jkpieterse pointed out, if the user insert cells or use cut operations, so I might have to do something about this. For many of these references I already use a combination of INDEX and MATCH referencing only to index cells in row 1 and column A, Which is hidden, protected and outside the input range. I think maybe if I use this solution on all references to the input range, the refferences will still be valid even if the user uses cut operations inside the input range.

By: Alastair

Alastair — Wed, 16 Jan 2008 13:34:00 +0000

but the vba restore code clears the undo buffer so the undo buttons are disabled? or have i missed something….

By: jkpieterse

jkpieterse — Wed, 16 Jan 2008 13:30:00 +0000

Well, you can schedule your undo macro to be run when the user clicks any of the default undo buttons:

Application.OnUndo "Description of Undo" , "YourUndoSub"