Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Excel / Programming / July 2008

Tip: Looking for answers? Try searching our database.

Application.Run, doesn't return to calling procedure

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Werner Rohrmoser - 31 Jul 2008 11:23 GMT
Hi,

after calling a procedure in another workbook with
Application.Run the program doesn't find back to
the calling procedure.

Are there common reasons for this behaviour?
Thank you

Regards
Werner

Excel XP SP3
Win XP SP3
Chip Pearson - 31 Jul 2008 14:28 GMT
Does the procedure called by Run execute properly? Is the procedure that
uses Run executed from a worksheet cell?

Signature

Cordially,
Chip Pearson
Microsoft Most Valuable Professional
   Excel Product Group
Pearson Software Consulting, LLC
www.cpearson.com
(email on web site)

> Hi,
>
[quoted text clipped - 10 lines]
> Excel XP SP3
> Win XP SP3
Werner Rohrmoser - 31 Jul 2008 17:11 GMT
Yes, the procedure executes and finishes properly.
It's started by an Command Button from the Forms Tool Bar, which is
located on a worksheet.

I fear I have to look deeper into my colleagues "spaghetti" program,
this was what I tried to prevent with my global question.

I tried some ideas, what might have caused the malfunction,
but only when I closed the workbook with the procedure I have called
by VBA than it doesn't come back.

Anyway thnaks for your reply.

Werner
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.