So am I!! Thanks again for your help

When you mean operating file, then I guess you mean data files that belongs to your application. Such files should not be placed in the Windows-directory. What if another application suddenly decides to also use this location, and by mistakes uses your filename-format ? You should read this guide from Microsoft Data and Settings Management[^] (Though written for Win2k, then it also holds for Vista/Win7) TCHAR szAppData[MAX_PATH]; ... hr = SHGetFolderPath(NULL, CSIDL_APPDATA, NULL, 0, szAppData); PathAppend(szAppData, "Company\Product\File.txt") CSIDL_APPDATA - Per user, roaming [user profile]\Application data CSIDL_LOCAL_APPDATA - Per user, non-roaming [user profile]\Local Settings\Application data CSIDL_COMMON_APPDATA - Hidden folder for normal users. Per machine (non-user specific & non- roaming) All Users\Application data CSIDL_COMMON_DOCUMENTS - Visible folder for normal users. Default files in this folder is readonly for other users than the creator, the application must change the security permissions on its application-folder to change this behavior. Per machine (non-user specific & non- roaming) All Users\Documents modified on Monday, December 14, 2009 10:39 AM

Hey Guys, Many thanks for all your help. It has poven very useful. All the Best Danny

No thanks but It was not bad link. :) Of one Essence is the human race thus has Creation put the base One Limb impacted is sufficient For all Others to feel the Mace (Saadi )

Hi, the problem with global data is every one can access them, which also means the compiler has to allow for data changes all the time, so the data needs to be reloaded into registers/accumulators all the time. One way to improve this is to use local pointers to point into your global arrays. So for each global array you are interested in, create a local (and constant) pointer that points at it, then keep using the local pointers. I have been designing two floating-point packages in a previous life, and I did study quite a lot of existing ones. I was very much surprised by the amount of code and complexity they were willing to add in order to shave off a few percents of execution time. So I doubt very much you would come up with something revolutionary, I would rather not trust your initial measurements; blowing away the current implementation by something that has awful accuracy is no good: the standard library has to be accurate up to 1 or 2 of the lowest bits. Of course, if your applications don't need such accuracy, there are certainly faster algorithms to get that. But don't let me discourage you, when and if you really get good results, I hope we will all hear from you. :) Luc Pattyn [Forum Guidelines] [My Articles] I use ListBoxes for line-oriented text, and PictureBoxes for pictures, not drawings.

Yeah thats right,;) Hi Alok how are you? I think its better I use of my name and also without any sig very simple.

VC7, VC7.1 or VC8. VC6 is very non conformant to the standard and the STL implimentation is plain terrible. Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )

I'm Confused, are you importing GIF files or Illustrator native files ( vector )? if they are GIF, there are tons of code that can be found here or with google that will do this. if they are Illustrator file, then you will have to do a bit more coding to support vector display in your application, and vector file import; I don't know if Adobe has a SDK to read those files. Maximilien Lincourt Your Head A Splode - Strong Bad

Danny Nowlan wrote: I implemented it and I had no errors, however the Combo box still isn't showing up. Sorry :) The limited example code didn't have enough style flags. try m_MyCombobox.Create(CBS_DROPDOWN|WS_VISIBLE|WS_CHILD, CRect(10,10,100,15), this, IDC_MYCOMBOBOX); Calling MyCombobox.ShowWindow(SW_SHOW) would make it show as well. Useful if you want to create it hidden and show it later I suppose. Mark

See WM_KEYDOWN/WM_KEYUP _** **_ WhiteSky

Understood, but a blanket statement like, "MFC, or even better, WTL." without any reasoning, is hardly useful. "One must learn from the bite of the fire to leave it alone." - Native American Proverb

for use within MFC I do not know the details myself. However if you send in an email to support@dundas.com they can send you the information you need. Just let them know you want to use the gauge in an MFC project. I believe that they have a wrapper class you can use. Troy

~RaGE();, The first article really helped. It discussed compiler optimisations, and the moment I turned it off it worked like a charm. Thank you so much. Danny

Okay, 'fail to boot up' would imply what? Not even RUN at all? Of course, if you even suspect your program is starting okay, then add more of your own error handling to the application and maybe write to a text log file only when something is wrong. Then your customers could send this file to you when your app will not 'boot up' on their machines. It IS entirely likely you are at least getting into WinMain unless a critical statically linked DLL is missing, in which case Windows would normally tell you that a required DLL is missing. I suspect, as do you, that some part of your framework or app path is failing, but there is no visible external notification. You need to bring that out, either with message boxes or with text file logging. I usually favor the text file logging, as the user does not have to retype or 'interpret' anything. They can usually e-mail you a text file.