Thanks for the help. For some reason I don't actually have that control in my visual studio. Think it is only with the older versions? Paddy

Thanks for the help thats exactly what I was looking for! No my compiler didn't like the double[] void Window(double data[]) attempt, ha ha! paddy

Excellent, thanks. Paddy.

Thanks for the help, So if I have a button on my toolbar IDT_BUTTON1, I can put in a Case IDT_BUTTON1: in my main WndProc and it should work? Paddy

I understand what you are saying, they are not the same thing but for this particular case changing the background colour will work fine for me. Thanks, Paddy.

Paddy wrote: It's non-MFC I'm using. Does this mean that my main window can't do anything until EndDialog is called? Yup, your main window will be frozen. An alternative is to use a modeless dialog, or use threads. Nish Author of the romantic comedy Summer Love and Some more Cricket [New Win] Review by Shog9 Click here for review[NW]

Thanks for the help, I was calling InitCommonControls() but I forgot to include the WS_VISIBLE flag when I was creating the status bar!

Thanks Dave, For some reason I can't add any member variables, the "variables" menu item is grayed out when I right click on a control in the dialog editor! It's ok coz I found an easier way of doing it using: SendDlgItemMessage(hDlg, ID_MYLIST, LB_ADDSTRING, 0, (LPARAM)"Hi there!"); Thanks for the help, Paddy.

I think you need to use casting - as follows: pBuffer1 = (PBYTE) malloc (INP_BUFFER_SIZE) ; pWaveHdr1->lpData = (LPSTR) pBuffer1 ; pSaveBuffer = (PBYTE) realloc (pSaveBuffer, 1) ; That should solve the compiler errors. Scott

My product MemWatcher[^] will help identify if you're leaking resources. /ravi Let's put "civil" back in "civilization" http://www.ravib.com ravib@ravib.com

Thanks for the help

Paddy wrote: One more question, whats the difference between a windows form and an inherited windows form? An inherited Winform is a cool little beast that allows you to inherit the WinForm from a WinForm that you create in another library (DLL) or you own project (if you compiler before you inherit). You can define one form as your base form with controls, then you inherit that form. It will build a form that looks just like the base form. You can add items to the form, you just cannot modify any of the items on the base form. But you can, at any time, modify the base form and those modifications will bubble up to all inherited forms.. Cool! This is good for a Wizard type window where you have a certian layout. Another use is to simulate a skinning window by creating the base winform with different graphics or colors then dropping in the any of the modified base class DLLs thus changing the appearance of all inherited WinForms that inherit from that base WinForm. There are many uses Inherited Forms! Rocky Moore

Thanks I'll give it a try when I get out here!

Thanks again James. This is what I expected to see out of the byte array. Yes, I would also be interested in knowing a "short and sweet" version of the ToByteArray. Before using this forum, I was trying to do the same thing with C# pointers; but, I could never get what I needed. Then I started looking for a "memcpy" function in C#. I am guessing that the Marshal Object sort of does the same thing as the C++ memcpy function. Thanks again, Tom McDaniel