Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

ACC2000: RunApp Macro Action Does Not Open MS Money Properly


View products that this article applies to.

This article was previously published under Q207650
Moderate: Requires basic macro, coding, and interoperability skills.

↑ Back to the top


Symptoms

When you use the RunApp macro action to open Microsoft Money version 4.0 or 5.0, the program does not open properly. The behavior varies depending on the version of Microsoft Money that you are using.

In Microsoft Money 4.0

The Microsoft Money splash screen appears on the screen, but you receive the following error message:
Not enough memory is available. If you have several applications open at the same time, you might need to close one of them before you start Money.
This behavior occurs even if Microsoft Access is the only application open at the time that you run your macro. When you click OK in the error dialog box, Microsoft Money quits.

In Microsoft Money 5.0

The Microsoft Money splash screen appears and you are prompted for a password if you have one, but the Microsoft Money program window does not open, and the program button does not appear on the taskbar. However, if you try to open Microsoft Money, you receive the following message:
Microsoft Money is already running.
If you are using Microsoft Windows NT and you start the Windows Task Manager, you see MSMONEY.EXE listed as a running process.

↑ Back to the top


Resolution

If you are using Microsoft Money 4.0 or 5.0, you can use the Shell() function in a Visual Basic for Applications procedure in place of the RunApp macro action to open Microsoft Money. To do so, follow these steps:
1.In the Database Window, click Modules under Objects, and then click New.
2.In the Visual Basic Editor, on the Insert menu, click Procedure.
3.Type RunMoney in the Name box, select Function under Type, and then click OK.
4.Type the following line of code in the created function:
Shell "C:\Program Files\Microsoft Money\msmoney.exe"
						
NOTE: The path to msmoney.exe on your computer may be different.
5.Save the module as ProgramFunctions.
6.Create the following new macro that uses the RunCode command, and save it as RunAppTest:
   RunAppTest Actions
   ----------------------------
   RunCode
      Function Name: RunMoney()
					
7.Run the macro.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

↑ Back to the top


More information

Steps to Reproduce Problem

1.Open the sample database Northwind.
2.Create the following new macro that uses the RunApp command, and save it as RunAppTest:
   RunAppTest Actions
   -------------------------------------------------------------
   RunApp
      Command Line: C:\Program Files\Microsoft Money\msmoney.exe
					
3.Run the macro.

Note that you see the behavior described in the "Symptoms" section.
The behavior described in this article applies only to Microsoft Money version 4.0 or 5.0. If you try to use the RunApp action to open Microsoft Money 98, you receive the following message:
Microsoft Access can't invoke the application using the RunApp action.

The path to the application is invalid, or a component of the application is missing.

Check the path in Windows Explorer or File Manager.
However, if you try to use the Shell() function described in the "Resolution" section of this article, you receive the following error message:
Run-time error '53':

File not found

↑ Back to the top


References

For more information about the Shell() function, in the Visual Basic Editor, click Microsoft Visual Basic Help on the Help menu, type Shell Function in the Office Assistant or the Answer Wizard, and then click Search to view the topic.

↑ Back to the top


Keywords: KB207650, kbprb

↑ Back to the top

Article Info
Article ID : 207650
Revision : 3
Created on : 1/26/2005
Published on : 1/26/2005
Exists online : False
Views : 327