Run Macro within a Macro, continue

Hi Diego_Garcia

It sounds like there is something in your "DeleteRowOnCell" Macro that is causing it NOT to return to "TransDatabase". Is there an End Statement in there perhaps?

If not, please post the "DeleteRowOnCell" macro in whole.

Couple of questions are you sure the code stops where you have said ie have you debugged the procedure?

Look for where the VBA line highlights yellow. Or does the procedure lock / freeze?

I’m not really a big fan of Personal.xls IMO and only in my opinion I would find this hard for maintenance and admin of the codes, I would op for modeling out so have the called procedure inside this project, or even in developments in the procedure stopping the need for a call statement until all is working well, then if needs be the fragmentation can take place. If the procedures are not very large I would keep all in the one procedure as much as possible and module out the one project.

Hope that makes sense.

Maybe check the call statement is working correctly a simple message box at the start will help this test and end sub straight after to stop the code running just for testing. Ie

Sub DeleteRowOnCell()
Msgbox(“Test Per XLS”)
Exit sub

‘ here will be your old codes now skipped

End sub

This will test that al is ok and the error is not in that module but in the calling statement.

Jack

BTW post back if you need more help and maybe post the two codes / procedures.

The End Statement and End Sub are 2 different things. See End Statement in the VBA help.