don´t use 2 forms, use 1 form and load userforms inside, like what i showed you before. I would use many form, for exemple, if i wanted to create a chat application (to load private chat windows). But ... you are the boss :-D i don´t know what you are trying to achieve. Good Luck :cool: nelsonpaixao@yahoo.com.br

And = & (bitwise 'and') Or = | (bitwise 'or') AndAlso = && (logical 'and') OrElse = || (logical 'or') You'll get into problems replacing the bitwise 'And' and 'Or' operators with the logical && and || operators. Conversion problems from VB are caused by the fact that many VB programmers misuse 'And' and 'Or' as logical operators (they will function as non-short-circuiting logical operators, but are designed to be bitwise operators). David Anton http://www.tangiblesoftwaresolutions.com C++ to C# Converter C++ to VB Converter C++ to Java Converter VB & C# to Java Converter Java to VB & C# Converter Instant C#: VB to C# converter Instant VB: C# to VB converter Instant C++: convert VB, C#, or Java to C++/CLI

Hi, I found a very quick method in the end using RtlMoveMemory: [DllImport("kernel32")] public static extern void RtlMoveMemory(IntPtr dest, IntPtr src, int len); System.IntPtr pBuffer2 = Marshal.AllocHGlobal(BufferSize); //Assign unmanaged memory RtlMoveMemory(pBuffer2, pBuffer, BufferSize); //Copy memory byte* p2 = (byte*)(void*)pBuffer2; // Use p2 to access image pixels Marshal.FreeHGlobal(pBuffer2); //Free unmanaged memory Thanks, for the help and hope this helps some one else.

I guess you can use System.Runtime.Interop.Marshal.AllocHGlobal to do that. I wouldn't do this in managed code at all but I guess it should work. led mike

Hi, you can perform calculations with pointer values: every time you add one you move to the next element of that type (same as in C or C++). Guffa's answer below gives you a detailed example for bitmapped images. :) Luc Pattyn [Forum Guidelines] [My Articles] Fixturized forever. :confused:

This is how you get the color components of a pixel, specified by the x and y coordinates: byte* p = (byte *)(void *)pBuffer; p += (x + y * Width) * 3; byte r = *(p++); byte g = *(p++); byte b = *p; If you increase the pointer for the last component also, it will point to the next pixel. This is very useful if you access the pixels in sequence, as you don't have to calculate a new address for each pixel. Despite everything, the person most likely to be fooling you next is yourself.