Oh I see, that's really cool! Thanks Hua-Ying

Thanks that really does work! I've always though that argument in a #define were separated by spaces so that it would see 3 arguments there. I guess I was wrong!

LOL, I have seen that problem and never knew why it didn't work. (Not like I really thought about it). You get it in your mind that you are declaring and instance and you don't even realize you are doing a prototype. Tim Smith I'm going to patent thought. I have yet to see any prior art.

Both suggestions were very helpful! Thanks Hua-Ying :)

I found it!! My project was generated by another program and it set the Preprocessor define UNICODE in the project. So it was in the Project Properites setting under C/C++ > Preprocessor > Preprocessor Definitions. This is the reason it didn't show up when I searched the code for #define UNICODE. Thanks for the help!! Hua-ying

Another approach is the following: void function(type1 parm1,type2 /*parm2*/) { //... } Commenting out the parameter name in the argument list guarentees that the parameter isn't used, since there is no longer a definition for it (the compiler will issue an error message otherwise). Software Zen: delete this;

You can also use GetFileAttributes() You can also use CreateFile and try to open Existing You can also use FindFirstFile You can also use CFile You can also use fopen :omg:

Interesting, I'll check. Thanks Hua-Ying

you're using firefox? the formatting options don't appear in ff. -jim

hyling wrote: Would you explain why you said this: Calling SetFocus() in a dialog (or anywhere else) can be problematic. I couldn't find anything discussions about this with google. You can and do get into race conditions where your code is trying to SetFocus and Windows is also trying to SetFocus(). A common mistake people make where this is evident is validating a control in its OnKillFocus() handler and calling SetFocus() when it is invalid to set the focus back to the control loosing focus. This won't work because upon return from OnKillFocus() windows will set the focus to the next control etc. PostMessage() is a way to handle this scenario. David has pointed out the correct answer however.:) Neville Franks, Author of ED for Windows www.getsoft.com and Surfulater www.surfulater.com "Save what you Surf"

Thanks, also useful for me

You're right, escaping the string isn't necessary unless it is a string literal. I was confused by the VS.net debugger, which puts a summary of the elements of the FILE structure beside the pointer, the first element of the FILE * happened to be "0(Bad Ptr)", but the FILE * itself was good. Err.. . maybe I just need more caffeine. :zzz: Now I know why nobody else on the net or discussion boards had problem... Thanks for your time. :-O Hua-Ying

Thanks for the link, it is interesting to see alternatives out there. Maybe it doesn't exist but what I'm looking for is a library that will allow me to call a function which will do just the right thing depending on which platform it is running on. Hua-Ying

Thanks for everyone's help!! :) For anyone else who's having the same problem, one last thing you must do before this solution will work is to add a variable in you main dialog class so that when it loads your control it will use the subclass for the control instead of the original. Details: using the class wizard generate a new variable with your subclass type, click the control check box (VS 2003 .Net) so that DDX_Control will update the value. You can also follow Chris Maunder's great tutorial on subclassing controls: tutorial Hua-Ying