See if there are any event delegates that you have missed. May be the code expects you to catch the callback on the container page.

Thanks for the reaction. I'm using controls designed by DevXpress, so i did a search on there forums as well. While there I stumble onto a similar problem. The problem could lay in a databinding control which could prevent events from firing. This second page exists out of a tab control with 4 pages. When I remove the 2 last pages the control starts working. So my best guess is that one off the bindings onto those pages misbehave. Thanks anyway Learn from the mistakes of others, you may not live long enough to make them all yourself.

How about the internet instead, it's far cheaper, current, environmentally friendly etc etc? Seriously. I haven't bought a programming book I really needed in over a decade. "Creating your own blog is about as easy as creating your own urine, and you're about as likely to find someone else interested in it." -- Lore Sjöberg

I certainly will ;) Learn from the mistakes of others, you may not live long enough to make them all yourself.

BadKarma wrote: small, meaningful assignments There is always the good old standby of the book/video/stamp/record CD collection. Honi soit qui mal y pongs - Evil to he who thinks it stinks

Graham Bradshaw wrote: Shouldn't ReDim nFoo(j - 1) be ReDim Preserve nFoo(j - 1)? As the code is, you reinitialise nFoo. Yes, you are correct. Thanks for pointing it out, must have slipped through my fingers while typing it over from the real code. :-O Note to myself: Learn to use Copy-Past ;) Learn from the mistakes of others, you may not live long enough to make them all yourself.

Hmmm thats interesting, it seems too simple to be a bug. Anyway its good you got it working. -Saurabh

BadKarma wrote: if (!AfxWinInit(::GetModuleHandle(NULL), NULL, ::GetCommandLine(), 0)) BadKarma wrote: Why is this? The CWinApp object theApp is never used. What does it do? Look up CWinApp constructor and then step into AfxWinInit, you will see that it needs a CWinApp object, see the call AfxGetApp(). AfxGetApp is able to get an application pointer due the following line in the CWinApp constructor. pModuleState->m_pCurrentWinApp = this; Some MFC specific initialization is also done in these functions and stored in thread local storage. This happens in AfxTls.cpp line number 100, comes via AfxClassInit(). Nibu thomas Microsoft MVP for VC++ Code must be written to be read, not by the compiler, but by another human being. Programming Blog: http://nibuthomas.wordpress.com modified on Thursday, June 12, 2008 8:51 AM

Actually just saying that MACROs are bad, is half knowledge. Many many platforms like MFC and ATL use MACROs extensively. The platform(Architecture) I work on is OS independent. In that case MACRO work as saviour. We can't use standard template because that would make code platform dependent so we have to USE MACRO to simulate templates. MACROs are an effective way to use the strength of preprocessor, if you use them correctly then they can really be useful. When some one says that avoid MACROs then the main intention is to avoid using it at the place of function. But the usage of MACROs are beyond that also where they would be indispensable.

I would have done it in binary like so: 1101010101001101110010100111010101010011011100101001 1010101010011011100101001110101010100110111001010010 0101010100110111001010011101010101001101110010100110 1101010101001101110010100111010101010011011100100101 1101010101001101110010100111010101010011011100101001 That way there's less confusion There are 10 types of people in the world, those who understand binary and those who dont.

Can't recall that I have seen such a behaviour in my networking applications. I wonder if you can go single threaded (from your postings it sounds that you are using an event based socket class with multiple threads)? /M

BadKarma wrote: while(pData < m_lpBufCur) byFoo = *pData++ ^= byFoo; They wanted to encrypt the encryption algorithm? :rolleyes: Cheers, Vikram. "But nowadays, it means nothing. Features are never frozen, development keeps happening, bugs never get fixed, and documentation is something you might find on wikipedia." - Marc Clifton on betas. Join the CP group at NationStates. Password: byalmightybob

Try calling SuspendLayout() showing the controls then calling ResumeLayout().

Are you absolutely sure you must do this? Developing a device driver is time consuming, especially so if you do not have prior experience. I'm currently fiddling with device drivers right now, and I can tell you that it's far more complex than writing a user space app. If you absolutely must write a device driver, I suggest you get a copy of Programming the Microsoft Windows Driver Model (ISBN: 0-7356-1803-8). What you need to do is to write a serial port minidriver - a driver which implements a serial device driver skeleton. -- 100% natural. No superstitious additives.

Thanks, So it just like i just found out, to prevent you to shoot yourself in the foot :-D codito ergo sum