tom-
thanks for your response... i tried it (at least how i interperete
what you wrote), however it did not work.
what happened is that my macro from workbook-A opened the userform i
workbook-B and filled it out, then paused. when i clicked th
"commandbutton" a msgbox popped up. i had to "OK" it, then th
commandbutton "action" happened. so it looks like i onl
"boobie-trapped" the commandbutton on the userform, i didnt actuall
get it to "click" from my macro in workbook-A. im confused...
i couldnt agree more about the method being flawed from the git-go
without getting too wrapped up in details, the nature of what i want t
do is very complex and has many steps.
- i developed a very large tool 'workbook-A'
- another engineer developed an even larger tool 'workbook-B'. his too
uses vast amounts of userforms to collect and display data (i kno
little about userforms, but much about macros in general, according t
me)
-combining workbooks wouldnt make this easier for me, i still need t
know how to activate his userform "commandbutton"s to automate ou
analyses. both processes are very iterative and do hundreds o
thousands of calcs (each) so i want to 'batch' all our macros togethe
so i (we) dont have to feed the workbooks any additional data after w
press the "go" button. the problem is his userforms are huge an
complicated and i dont want to look through all the code to bypass th
form... id rather fill the userform out like he wanted and submit the
like they would normally be done. BTW he is no longer here, so thi
makes it very difficult.
please, can you instruct me one more time... last time it didnt work.
thanks