Search:

Having RC in different DLLs you should use AfxGet/SetResourceHandle or
AFX_MANAGE_STATE ( AfxGetStaticModuleState() ); depending from type of DLL

1. Yes
2. No

In this case you should enumerate all shared folders and map them one by one. BTW I don't think you will succeed with ftp server

Because console output( as well as other file output ) is buffered

I assume that you output job results upon finishing job.
Try to use fflush(NULL) for child process at the end of job

1. PeekNamedPipe is applicable to anonymous pipe as well
2. Probably the problem is your child process

Now MSDN offers better code under the title

"Creating a Child Process with Redirected Input and Output"

Usage PeekNamedPipe could help as well

You are absolutely right, but in this case you will have to provide your own UI

I don't understand you. Could you show your code?

I don't think that UPDATE_UI works for dialogs. You should do it explicitly by yourself

Yes, try EnumThreadWindows

ShowWindow does work. I guess yours FindWindow doesn't work properly

GetParent()->GetDltItem(IDOK)->)->EnableWindow(FALSE);

What about GetUserName

Use CreateDC

#include <afxdao.h>

Exactly as for internal resources. Add
#include "DLLresource.h"
and, for example

CString str;
str.LoadString(IDS_MESSAGE), where IDS_MESSAGE is ID of string resource from DLL

CLog c;
char str[200]={0};
HANDLE hMutex = CreateMutex(NULL, FALSE, "MyProtectedErrorHandling");
for(int i=0; i < 18000; i++){
sprintf(str, "Line:%d Message:Inside the loop, Handle:0x%x", i,...

Override OnCloseDocument( ); for your document class

I guess that strSource or strTarget or both of them are incorrect

For subitems use LVIF_STATE and LVIS_STATEIMAGEMASK mask

state
Indicates the item's state, state image, and overlay image. The stateMask member indicates the valid bits of this member.
Bits 0...

Yes, You are right. Actually I understood what is the problem. You should try to specify WS_CHILD instead of WS_POPUP. Otherwise your window isn't considered as child

1. You use wrong version of CreateEx. Use
BOOL CreateEx(DWORD dwExStyle, LPCTSTR lpszClassName, LPCTSTR lpszWindowName, DWORD dwStyle, const RECT& rect, CWnd* pParentWnd, UINT nID, LPVOID lpParam =...

Because in order to process SendMessage or GetWindowText which involves SendMessage, thread should get to it's message loop. If thread is busy by some other processing, you should wait. I guess you...

Sure you could. Just take care that you deal with the same hDC