CFileDialog problem???

Friends

I get a strange problem on the following code...

CString cstrInitialFileName = "Something.dat";
CString szExt("dat");
CString sFilter(_T("Curve Files (*.dat)|*.dat|All Files (*.*)|*.*||"));
         
CFileDialog dlg(TRUE, szExt, cstrInitialFileName, OFN_HIDEREADONLY | OFN_OVERWRITEPROMPT, (LPCTSTR) sFilter, NULL);

if (dlg.DoModal() == IDOK)
   CString cstrFileName = dlg.GetPathName();



If I run this code on Windows NT 4.0 and see the Task manager, there is an addtional thread is creating for this opendialog box and which is not releasing. but same code if run on windows 2000, the number of additonal thread count iam getting more than 4, and sometime its grows.

Friends do i have take any additional steps inorder to call CFileDialog on windows 2000????

Expecting some suggetions!!!
Thanks
Hari

pphariAsked:
Who is Participating?
 
migelConnect With a Mentor Commented:
Hi!
it is behavior by design - File Common dialog uses extra threads to access file system info (dirs tree and so on)..
You can`t restrict this (except you write your own dialog from scratch)
Good luck.
0
 
DanRollinsCommented:
Also, it is nothing to worry about.  It is not a massive resource leak.  Just a couple of tallies that make no difference to anything.

-- Dan
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.