Msg box error problem

[julhs]

I’m not sure what caused the WB to become unresponsive but given a while it recovered and appeared to be OK.
But now I find that ALL my MsgBoxes (that previously worked ok) cause,

Compile error:
Wrong number of arguments or invalid property assignment.

Has anyone got any suggestions as to why this is now happening?

 

[Joe4]

I’m not sure what caused the WB to become unresponsive but given a while it recovered and appeared to be OK.
But now I find that ALL my MsgBoxes (that previously worked ok) cause,

Compile error:
Wrong number of arguments or invalid property assignment.

Has anyone got any suggestions as to why this is now happening?

Can you shows us an example of how you have coded one of these message boxes?
And can you confirm that you are still using Excel 2010?
Did you go through any Office upgrades or updates lately?

 

[julhs]

Here’s the one that I was modifying when the WB to become unresponsive.

MsgBox "There is a name in the Suppliers column that you've NOT" & vbCrLf & "created a Named Range for. You need to go and create it."

Yes 2010
No upgrades
But problem is not just with above Msg box its EVERY SINGLE Msg box.
Have rebooted, problem still remains!!
UNFORTUNATLY when I went to my external hard drive that is set to update every 10 mins, I found that it had not done so
for 18hrs, on investigation found the lead had become dislodged.
So I am praying!!

 

[Joe4]

Try creating a new blank file, and creating a simple procedure with just one message box, like the one you show above.
Does that work?

If that does, that would suggest that maybe that particular workbook having the issues has become corrupted.

 

[julhs]

Been doing just that and ANY new MsgBox works OK
So I afraid that your assumption is correct, going to be a right royal task (due to amount of changes since last external HD save)
Give me strength!!
Thinking I was only one line of code away from putting this WHOLE thing to bed was little too good to be true
As a by the way this is part of developing what you gave me in:
Find Active cell value in another column and select it

 

[Joe4]

If you have a good backup from when before the error started, maybe you can restore that and build from there.

Otherwise, you can probably start a new workbook, and copy all the VBA code from the bad one into the new one.

 

[julhs]

Hay !!! with:

Otherwise, you can probably start a new workbook, and copy all the VBA code from the bad one into the new one.

You maybe have just saved me !****! of time, the codes weren’t wrong as they had previously worked BEFORE WD got corrupted.
So doing that would avoided the need to remember ALL the the changes I’ve made since the last HD save, (which was going to be a nightmare)
Going to take me a while to do this, but will let you know.