CString has the address of the memory location I think.

You're a good man. . .I'll give it a try. So I just download all of the office 97 patches. . .COOL! Thanks again, Aaron.

Anyone know how to get Access 97 to work with Windows XP?

Did you #include "resource.h" in the source or header file?

Anyone know if Access 97 can work on Windows XP. Hoping there is a conversion, 'cause I can't get it to work HELP

Does the application used for launching the two different applications dependent of those application? What I mean is. . .is the command line application included or attached to the two different applictions? If not you can query the system by the title of the two different application, and execute them depending on your logic. Aaron.

void CMyApp::OnLButtonDown() { AfxGetApp()->DoWaitCursor(1); // 1->>display the hourglass cursor // do some lengthy processing AfxGetApp()->DoWaitCursor(-1); // -1->>remove the hourglass cursor } What you are talking about, you might have to deal with CPoint. Use CPoint to get the location of the cursor in accordance to the location of the window. When the cursor is at a certain location in the window, such as, over a button. . .an action takes place to change the cursor. I know ActiveX controls have this ability. Check them out.

void CMyApp::OnLButtonDown() { AfxGetApp()->DoWaitCursor(1); // 1->>display the hourglass cursor // do some lengthy processing AfxGetApp()->DoWaitCursor(-1); // -1->>remove the hourglass cursor } What you are talking about, you might have to deal with CPoint. Use CPoint to get the location of the cursor in accordance to the location of the window. When the cursor is at a certain location in the window, such as, over a button. . .an action takes place to change the cursor. I know ActiveX controls have this ability. Chech them out.

You can use your CWinApp derived class in either a Dialog based application, or Multi/Single based app. What you do is create a CString variable in that derived class and load it by GetProfileString( LPCTSTR lpszSection, LPCTSTR lpszEntry, LPCTSTR lpszDefault = 0 ); Such as: class header: class CWhateverClass { . . . private: CString FileName; } class source: BOOL CWhateverClass::InitInstance() { . . . FileName = GetProfileString( "Saved", SavedFileName, FileName ); . . . } int CWhateverClass::ExitInstance() { . . . WriteProfileString( "Saved", SavedFileName, FileName ); . . . return CWinApp::ExitInstance(); } You are able to manipulate the CString FileName from other parts of your app by using theApp. Hope I hit what you were getting at. Aaron

You can do this by ON_COMMAND messaging. ON_COMMAND messaging sends or pumps a message to your entire program. It gets very tricky when sending messages from one Dialog class to another. The best programming with respect to Dialog based programs, is to keep your Views ( Dialog ) loosely coupled from the inner workings ( Control ). Some go on the idea of MVC ( model, View, Control ) idea. Try to read up on this. Another way is to implement a GoF concept, by using the "Observer pattern" ( plenty of example here in codeproject ). This pattern does the job of keeping the Dialog class loosly coupled, and is continually updated when information is changed, or an action has taken place ( hint: such as a radio button clicked ). All in all, messaging from one dialog to another has its pitfalls.