Filing Macro - Run time error '13: Type Mismatch

Hi All,

I've been working on this code for a while and can't seem to get it right. The code basically copies the integer value from one cell and deposits it in another worksheet. The problem I'm getting is a 'Run time error '13: Type Mismatch' although it doesn't seem to be this, to my knowledge anyway.

The code is as follows;

Please Login or Register  to view this content.

The message box displays the values in the column first defined, in this case "E". It doesn't appear to be seeing the 'Else' statement, it just seems to give the error if there is nothing in the "E" column. An example of this is that the message box provides the values from the "E" column, up until a "D" column value is present, at this point an error message pops up. If I go into debug I can change the first 3 lines of code to "D", ref below;

Please Login or Register  to view this content.

The code will execute and values appear in the message box.

This has been going on for months, some help would be hugely appreciated!

Look forward to your reply guys and girls, and thanks in advance.

Best,
W

Hi Norie,

Thank you for replying so quickly.

I've uploaded the whole work book. The reason I've done this is the code on a few test worksheets works, it's just with the work sheet I need it to work on, it doesn't. I have a feeling it might be a data issue, but if it is, I am still unsure how I would correct it.

If you want to look at the 'Transactions' and 'Table2' tabs for the working code. If you want to look at the 'BR(D)' and 'DACG (DCard)' tab for the code which isn't working.

The code is suppose to take income and expenditure out of the bank statement and filing them in the according worksheet. It works in the example but not in the actual and I don't know why, the code is identical, bar the cell referencing.
Non Private Version.xlsm
Best,

W

Hi Norie,

I've uploaded an adjusted version that provides the error. I simply changed the range for ddate to $A$66. This works fine for the purpose of displaying the error. If, however, once the error is adjusted it's going to be stuck in the loop again, how would you recommend stopping this from occurring?

I have cut a lot of data, only because the file size was so large. It went back to May of last year.

Please see attached.

Best,
W