Windows API has the function GetTopWindow GetTopWindow function (Windows)[^] From the TopWindow you want walk down thru the chain via GetNextWindow GetNextWindow function (Windows)[^] So in your case you want to ask the topWindow of the window that contains both FileZilla window and a Notepad Window. You can then walk along the chain using GetNextWindow and see which is above which just by asking the window title. Something like this will work char buf[256]; HWND Wnd = GetTopWindow( /*handle of window containing both*/ ); GetWindowText(Wnd, &buf[0], sizeof(buf)); while (Wnd != 0 && !stricmp(&buf[0], "FileZilla") && !stricmp(&buf[0], "NotePad")) { Wnd = GetNextWindow(Wnd, GW_HWNDNEXT); // Next window GetWindowText(Wnd, &buf[0], sizeof(buf)); // Get it's title } if (Wnd == 0) { /* Error neither window found */ } else { /* Wnd is the topmost of 2 windows title and the string title is in buf */ } It is equivalent to EnumChildWindows function (Windows)[^] However for the simplicity you have it isn't worth setting up the enumeration function. In vino veritas

Thank you, works like a charm. ;) "The Only Limit Is Only Your Imagination."

Yes. Politicians are always realistically manoeuvering for the next election. They are obsolete as fundamental problem-solvers. Buckminster Fuller

Blood_HaZaRd wrote: gcc test.cxx Foo.cxx -o Test.o This is not correct, the output should be your executable file Test (note executables do not have .o extension). You should then be able to run your program by typing Test at the command prompt. Take a look at the man pages for gcc for more information on compile and link options. Unrequited desire is character building. OriginalGriff

My mistake is that i missed to include the alias into the connectionstring. Thx for the reply. ;) "The Ultimate Limit Is Only Your Imagination."

use 'Object' tag in html. http://www.w3schools.com/TAGS/tag_object.asp[^]

Hi, Yes indeed,, in fact i installed Direct X developper + SDK 2003 and SDK 2008. But when i use VS 6.0 it doesnt work but with VS 2005 it does. i think that the SDK 2003 doesnt includes all necessary files or the project i tried to compile is based on headers of not 2003. Any way, Thank you for your reply that was a nice hand help. "The Ultimate Limit Is Only Your Imagination."

I believe you would want to send TTM_DELTOOL message to your existing tooltip control to delete the current text, followed by a TTM_ADDTOOL message with the new text. Alternatively, I think you can use TTM_SETTOOLINFO to modify the text of an existing tooltip - that may be simpler. The following snippet shows the syntax for TTM_ADDTOOL and may point you in the right direction, although the code is WTL instead of MFC: TOOLINFO info; ZeroMemory(&info, sizeof(TOOLINFO)); info.cbSize = sizeof(TOOLINFO); info.hinst = \_Module.get\_m\_hInst(); info.uFlags = ( TTF\_CENTERTIP | TTF\_ABSOLUTE); info.lpszText = \_T("Your new text here."); m\_Toolbar.GetItemRect(m\_Toolbar.CommandToIndex(ID\_TOOLBAR\_BUTTON\_TO\_CHANGE ), &info.rect); info.hwnd = m\_Toolbar.m\_hWnd; info.uId = ID\_TOOLBAR\_BUTTON\_TO\_CHANGE; ::SendMessage(tt, TTM\_ADDTOOL, 0, (LPARAM)&info);// tt is the HWND of the tooltip control L u n a t i c F r i n g e

I think you need to spend some more time reading about floating point number representations. A floating point (double) number allows you to store extremely large or extremely small values and anything in between, but at a cost of accuracy in these values. Thus they are no good for applications where numeric accuracy is important, e.g. anything to do with money. When you display such numbers on screen or printer you have various options for how you wish them to be represented on screen: in scientific 1.3456e-2, or decimal 0.013456 etc. If you want to use very large numbers with no loss of accuracy then you need to find a library or class (or write one) that can do it for you. It's time for a new signature.

I'm a bit confused: 0xE97804B9A34AB4E fits in an __int64 with a nibble to spare. I know it depends what your compiler is and __int64 isn't a standard type but if you've got it and it doesn't need to be portable then why not use it? Ash PS: I'm normally against using non-portable code but at least someone trying to compile your code for a platform with a 64 bit int would at least be warned something was up. PPS: And if you need to store it in 32 bit values you can take advantage of some properties of ints that makes it relatively easy to calculate the modulus.

Blood_HaZaRd wrote: Ah no indeed i'm using MF For another project? The posted one looks the classical console application... :rolleyes: If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile. This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke [My articles]

Thank you soo much the first one runs great the secondm francly i didn't undestand it so i ll try it later :laugh: anyway thank you again for your great help :thumbsup: "The Ultimate Limit Is Only Your Imagination."

@ Garth: Sorry for deleting the message, i thought it was like in other forums when it's solved we may delete it to avoid the dump. @ Aescleal: I found a wasty manner to solve my prob (OnKeyDown related) which is void CSdiView::OnKeyDown(UINT nChar, UINT nRepCnt, UINT nFlags) { // TODO: Add your message handler code here and/or call default if((nChar<=0x30)&& (nChar>= 0x39)) AfxMessageBox("Number"); CFormView::OnKeyDown(nChar, nRepCnt, nFlags); } BOOL CSdiView::PreTranslateMessage(MSG* pMsg) { // TODO: Add your specialized code here and/or call the base class BOOL bHandleNow = false; switch (pMsg->message) { case WM\_KEYDOWN: switch (pMsg->wParam) { case 0x39: case 0x38: case 0x37: case 0x36: case 0x35: case 0x34: case 0x33: case 0x32: case 0x31: case 0x30: bHandleNow = TRUE; break; } if (bHandleNow) OnKeyDown(pMsg->wParam, LOWORD(pMsg->lParam), HIWORD(pMsg->lParam)); break; } return bHandleNow; } but i m only able to detected Numbers and Upper Cases Letters like A-Z and no a-z (another problem but at least i was able to detetect numbers an capital letters :rolleyes: "The Ultimate Limit Is Only Your Imagination."

It seems the best way, after all spending 4 hours looking for a function or a sample code is stupid ;P I created a CEdit based class, called CTest in whhich i add the OnKeyDown(...) Now how could call it from the OnChangeEdit1 Function of my CFormView? PS: I need to pass the 3 parameters UINT of OnKeyDown << Newbie question sorry "The Ultimate Limit Is Only Your Imagination." modified on Tuesday, June 8, 2010 1:36 PM

Ok here some news, i compiled my project under wind2003 with MVS6.0 only installed and it works, no error message like Error DllServer. All is green and i'm happy :-O . But may be the question how could we fix the prob of DllRegister under a PC with more than 1 MVS installed. :^) "The Ultimate Limit Is Only Your Imagination."

Not sure who gave me a 1 vote... but HRESULT 0x8007007e means "The specified module could not be found". if this is occuring during DLL registration then it is a missing dependency. Best Wishes, -David Delaune

COM is the foundation ActiveX is build upon. DLL hell was just one of the problems COM was designed to solve, and it's not the major one. Essentially COM is a technology designed to provide language independent binary components. Steve

for that error it was the " that i added to the path when including the lib. now it's gone when i erase it ;) For the oci, i m trying to put on screen the data from an Oracle DB using C++ and this to integrate it into a larger team work. so my part is to begin with the ocilib driver. "The Ultimate Limit Is Only Your Imagination."

I guess scanf is always returning a value > 0 in ur code. You would want to use a getch() like function to detect keypress rather than scanf. Check this out http://cboard.cprogramming.com/archive/index.php/t-27714.html[^] ------------------------------------------- It's code that drives you - Shyam