AddItem insert the text in the FixedRow for example: AddItem("nnnn", 2) insert the text in the second row of the fixed column If you want to insert data in a FlexGrid you need to set teh Row (SetRow), then the column (SetCol) and then SetText for insert the text in that Row and column. If you need to read you can use the function GetText. Good Luck :bob: Carlos Antollini.

The reason you get a debug assertion is so you can go into the debugger and see where the ASSERT has failed, and therefore do something about it. Often it doesn't actually kill your program, it is warning you however that you've leaked memory or done something else that needs cleaning up. I'd suggest if you have this problem in future, you look at where it is occuring, and if you can't fix it, post where it crashes as well as the block of code that is crashing. Christian As I learn the innermost secrets of the around me, they reward me in many ways to keep quiet. Men with pierced ears are better prepared for marriage. They've experienced pain and bought Jewellery.

In general, a handle is just a 32-bit key to a data structure maintained by Windows. Some common handles are: HACCEL - Handle to an accelerator table. HANDLE - Handle to an object. HBITMAP - Handle to a bitmap. HBRUSH - Handle to a brush. HCOLORSPACE - Handle to a logical color space. HCONV - Handle to a dynamic data exchange (DDE) conversation. HCONVLIST - Handle to a DDE conversation list. HCURSOR - Handle to a cursor. HDC - Handle to a device context (DC). HDDEDATA - Handle to DDE data. HDESK - Handle to a desktop. HDROP - Handle to an internal drop structure. HDWP - Handle to a deferred window position structure. HENHMETAFILE - Handle to an enhanced metafile. HFILE - Handle to a file opened byOpenFile, notCreateFile. HFONT - Handle to a font. HGDIOBJ - Handle to a GDI object. HGLOBAL - Handle to a global memory block. HHOOK - Handle to a hook. HICON - Handle to an icon. HIMAGELIST - Handle to an image list. HIMC - Handle to input context. HINSTANCE - Handle to an instance. HKEY - Handle to a registry key. HKL - Handle to a keyboard layout. HLOCAL - Handle to a local memory block. HMENU - Handle to a menu. HMETAFILE - Handle to a metafile. HMODULE - Handle to a module. HMONITOR - Handle to a display monitor. HOOKPROC - Pointer to an application-defined hook function specified toSetWindowsHookEx. HPALETTE - Handle to a palette. HPEN - Handle to a pen. HRGN - Handle to a region. HRSRC - Handle to a resource. HSZ - Handle to a DDE string. HTREEITEM - Handle to an item in a tree-view control. HWINSTA - Handle to a window station. HWND - Handle to a window. /ravi "There is always one more bug..." http://www.ravib.com ravib@ravib.com

Read the help file, boy. It is the file c:\Winnt\Help\MsFlxGrd.hlp or c:\Windows\Help\MsFlxGrd.hlp

Thank you very much,your answer was very useful ...:) AHMAD ALWASHALI

Your problem is that a CString object does not contain the string itself, only a pointer to the string. When you write your omega object to the file, you only write the pointer, which is then invalid when you read the object back in and try to use it. --Mike-- http://home.inreach.com/mdunn/ All your base are belong to ME~!

The compiler can't know anything about classes inside .lib files, they are only used in the link phase. The CImage class must be declared in a source file (.cpp or .h) so that the compiler can see it.

I'd hazard a guess and say you're developing under Win9x. I had the same thing a little while ago (I'd never seen it before, even on much larger projects). The solution I found was to setup the virtual memory settings myself, rather than let the OS manage it (actually, this isn't a bad idea on a development machine, since it can reduce swapfile fragmentation). I hope this helps! Andy Metcalfe - Sonardyne International Ltd (andy.metcalfe@lineone.net) http://www.resorg.co.uk "I used to be a medieval re-enactor, but I'm (nearly) alright now..."

There is a project at CodeProject that demonstrates skinnalbe apps by providing full source for an mp3 player. I have successfully removed the player classes and played MP3s in my own code. XAudio is free, but it has a license agreement which basically states that they are free to decide one day that they want money for it, so I'd recommend not using it. I'd prefer to know up front if something is going to cost me, and how much. Otherwise, who knows what could happen down the track ? In that vein, fmod is a sound library that appears quite powerful, is free for use in non profit code, and gives you up front prices if you're going to use it in commercial code. Christian The content of this post is not necessarily the opinion of my yadda yadda yadda. To understand recursion, we must first understand recursion.

Thank you very much :) AHMAD ALWASHALI

Thank you very much AHMAD ALWASHALI

Thank you very much AHMAD ALWASHALI

THANK YOU VERY MUCH AHMAD ALWASHALI

Thats simple: usually u use a command like (HIWORD)(lParam) ! That means you want to have the upper 16 Bit from 32. To get them you have to shift right 16 (>>16) times and mask out the upper 16 Bit ( & 0x0000ffff ). To get (LOWORD)(lParam) you have to clear the upper 16 Bit. Converting to a new type WORD from DWORD takes only the lower 16 Bit. The effect is the same. Hope it helps Greatings Mario/// -------------------- www.klangwerker.de rocknix@lycos.de --------------------

You could do something similar: [ccode] #include using std::ostringstream; void Func() { int a; int* p = &a; ostringstream stream; stream << p; SetDlgItemText(IDC_EDIT1, stream.str().c_str()); } [/ccode] Walter Gildersleeve Freiburg, Germany walter.gildersleeve@pe-gmbh.de

hi, PASCAL is used in all exported function declarations, indicating to the compiler that Pascal rather than C ordering is used for all arguments (values) pushed onto the stack. While C commonly uses inverted order, placing the least-significant bytes first on the stack , Windows uses Pascal ordering that, like Unix, places the most-significant bytes first. There is another small but crucial difference. Exported functions are functions that will be called from outside the class or in the case of a DLL from other applications outside the unit (library). In a Windows application where subroutines are called from Windows itself or where a member function in one class is called from outside the class, even if both belong to the same application, the Pascal calling order is necessary. On the other hand, all internal function declarations (functions and subprocedures called directly from other procedures within the application) will expect arguments to appear in standard C order and should not be declared using the PASCAL specification. As far as how argument lists are declared in the procedure definitions, it makes absolutely no difference whether the Pascal or C calling conventions are used. These conventions affect only how the arguments are handled internally that is, on the stack and do not in any way affect how the programmer constructs the argument lists. However APIENTRY will end up defined as WINAPI when you include windows.h in version 6 , WINDOWS.H now supports the WINAPI macro, which translates to the appropriate calling convention for the target. Use WINAPI where you previously used PASCAL or __far __pascal. for the actual definitions see windef.h -- Basic Windows Type Definitions cheers

You stop it by overriding OnOK and OnCancel. You can make the buttons still work by checking the keystate with GetKeyState(VK_RETURN) (or VK_ESCAPE) and returning if they are down. Then your button works, but the key does not. Christian The content of this post is not necessarily the opinion of my yadda yadda yadda. To understand recursion, we must first understand recursion.