See Here[^] maybe it is some helpful to you you need to override OnOk and OnCancel_** **_ whitesky

Im not sure but maybe you can hide scrollbar with these functions ShowScrollBar or BOOL o=InitializeFlatSB(hWnd); o=FlatSB_ShowScrollBar(hWnd,SB_BOTH,0);

i think u can do it from dll attach of the extension dll nave

See CDocument::UpdateAllViews()  onwards and upwards...

Your best bet is to look at Microsoft's converted VC6 sample macros that have been converted to VB .NET. (They're in the file DevStudio6Editor in MacroExplorer.) Then study the differences and work from there. There is also a specific VS add-ins and macros Yahoo group you could try posting to here: http://groups.yahoo.com/group/vsnetaddin/?yguid=75841244[^] Kevin

UserTable with UserID and Email address CategoryTable with CategoryID and UserID When a change to a category occures, you would search the CategoryTable for the CategoryIDs you want, get the associated UserIDs, then search the UserTable with the UserID to get the email addresses.

That is not a complex dialog! If you want to centralise (create a handler) the control of any change messages, then you write one function that can handle any change and have have all the the change messages rerouted to that handler. What that means is that you have your on-change functions for each control call the same function to handle the message. On a more practical note; each on-change function should do it's own thing and then call a funcion that, that says "wow, something has changed so we have to update the current status" (display, whatever...) and act accordingly. Of course you could write a hook, to handle the messages, but that is a more than a bit of overkill for simple message handling. You could also handle the messages in PreTranslateMessage(...), which is almost the same as writing your code in C (one message handler for the whole window). Those are the choices I see, but essentualy what you appear to need is just a function that needs to be called it any changed occured. (See "On a more practical note") Good Luck! INTP "The more help VB provides VB programmers, the more miserable your life as a C++ programmer becomes." Andrew W. Troelsen

thankyou. the answer was helpful Raghu

in one sentence. Semaphore can be used to manage resources, criticalsection to synchronize access to shared data within same(single) process and mutex to synchronize access to shared data among different process also. There is no spoon. mail

Have you tried putting try and catch around your socket code? In doing so you may be able to get a better idea of the exception. Ant. I'm hard, yet soft. I'm coloured, yet clear. I'm fruity and sweet. I'm jelly, what am I? Muse on it further, I shall return! - David Williams (Little Britain)

Hi, You can read this articles: ListBox With ToolTip Support[^] And List Box with ToolTips[^] Ivan Cachicatari www.latindevelopers.com

Hi, Mine is an SDI application where I do like this: CSingleDocTemplate* pDocTemplate; pDocTemplate = new CSingleDocTemplate( IDR_MAINFRAME, RUNTIME_CLASS(CConvertDoc), RUNTIME_CLASS(CMainFrame), RUNTIME_CLASS(CConvertView)); AddDocTemplate(pDocTemplate); in my initinstance CMainFrame is derived from CFrameWnd and CConvertView is derived from CEditView. Is there any problme in this kind of creation? Regards Raghu

This is caused by the form view's default implementation. A click on the Enter key issues a command for the form to simulate a click on it's default button, which usually is the 'OK' button. In your case, it is the button 1. To remedy this, change the button 2 to be the default button of the form, or alternatively, capture keyboard messages sent to the form and filter out those containing VK_RETURN. This prevents the form from calling the default button's BN_CLICKED handler when it receives a key press event indicating the Enter/Return key was pressed. Of course, when you filter out the keyboard messages, you can custom-call the click handler for the second button as well. To simulate a click on a button, create a WM_COMMAND message, put the HIWORD of wParam to be 'BN_CLICKED' and LOWORD to be the ID of the control. The lParam can be left alone (NULL) or can be the window handle (HWND) of the control. -Antti Keskinen ---------------------------------------------- The definition of impossible is strictly dependant on what we think is possible.

:) if you broadcast a message, all the apps are geting it and if they have a function mapped to this message, you get funny results. you mustnt broadcast a message. send it to a particular window.