I have two macros that I run together in another macro. Both work well if
used independently but when run as part of third macro, designed purely to
bring them together, it stops after running the first macro.

The first macro (the converter) takes data from another application and
converts it into a usable fromat. The second macro (the transferor) transfers
the usable data to my main application.

Both run perfectly well if I run them as independent procedures.

However when I bring them together in a third macro to make conversion and
transfer a seamless process the transferor macro does not even begin to work.

I have tried adding the transferor code to the ned of the converter macro,
still no joy, it stops at the ned of the conversion procedure.

Is this Excel's way of telling me that any extension of the converter makes
the procedure too long.

Help please!!!!!!


Dave

Have you placed a break point on the call to the transferor macro in the main
sub that calls both the converter and transferor. If so what happened when it
got to that line... or did it get to that line? Are you using end subs
anywhere that may be stopping things? Hard to tell without more info...

"dave glynn" wrote:

I have two macros that I run together in another macro. Both work well if
used independently but when run as part of third macro, designed purely to
bring them together, it stops after running the first macro.

The first macro (the converter) takes data from another application and
converts it into a usable fromat. The second macro (the transferor) transfers
the usable data to my main application.

Both run perfectly well if I run them as independent procedures.

However when I bring them together in a third macro to make conversion and
transfer a seamless process the transferor macro does not even begin to work.

I have tried adding the transferor code to the ned of the converter macro,
still no joy, it stops at the ned of the conversion procedure.

Is this Excel's way of telling me that any extension of the converter makes
the procedure too long.

Help please!!!!!!


Dave

No. That is not Excel's little way of telling you your code is too long.
Excel generally speaks in the form of error messages.

Define "does not even begin to work". Do you get an error. Does the code
just stop (do you have error handling). Where is the third macro located?
Do you use code like

Range("A1").Select
Selection.Value = 3
Worksheets("Sheet3").Activate
Range("B9").Select
Selection.copy


Have you tried

Sub ThirdMacro()
converter
transferor
End Sub

--
Regards,
Tom Ogilvy

"dave glynn" wrote in message
...
I have two macros that I run together in another macro. Both work well if
used independently but when run as part of third macro, designed purely to
bring them together, it stops after running the first macro.

The first macro (the converter) takes data from another application and
converts it into a usable fromat. The second macro (the transferor)
transfers
the usable data to my main application.

Both run perfectly well if I run them as independent procedures.

However when I bring them together in a third macro to make conversion and
transfer a seamless process the transferor macro does not even begin to
work.

I have tried adding the transferor code to the ned of the converter macro,
still no joy, it stops at the ned of the conversion procedure.

Is this Excel's way of telling me that any extension of the converter
makes
the procedure too long.

Help please!!!!!!


Dave