C / C++ / MFC

//Adds a string in ComboBox
   CComboBox *combo = new CComboBox();
   combo->m_hWnd = GetDlgItem(IDC_TEST)->m_hWnd;
   combo->AddString("AS");  
   combo->AddString("ZX");  //Adds a string in ComboBox at Last Position
                            //if 'Sort' option is not Selected.

//Following shows the text in ComboBox (must not be in the list of ComboBox)
   m_combo = "ZX"; //where 'm_combo' member variable of 'IDC_TEST' ComboBox
                   // datatype of 'm_combo' is 'CString'
   UpdateData(FALSE);

BlitzPackage wrote:

when I run the app, it prompts me to decide what type of document to start with

"The largest fire starts but with the smallest spark." - David Crow

"The largest fire starts but with the smallest spark." - David Crow

Favorit.m_strFilter="User='"+myUser+"' AND Dokument='"+Number+"'";
Favorit.Open();
if(!Favorit.IsBOF())
{
    Favorit.MoveFirst();
    Favorit.Edit();
}
else
{
    Favorit.AddNew();
    Favorit.m_User=myUser;
    Favorit.m_Dokument=Number;
    Favorit.SetFieldNull(&(Favorit.m_Gelesen));
}
Favorit.m_Favorit=bChecked;
Favorit.Update();
Favorit.Close();

//{{AFX_FIELD(DBFavoriten, CRecordset)
CString m_Dokument;
CString m_User;
long    m_Favorit;
CTime   m_Gelesen;
//}}AFX_FIELD

DBFavoriten::DBFavoriten(CDatabase* pdb)
	: CRecordset(pdb)
{
	//{{AFX_FIELD_INIT(DBFavoriten)
	m_Dokument = _T("");
	m_User = _T("");
	m_Favorit = 0;
	m_nFields = 4;
	//}}AFX_FIELD_INIT
	m_nDefaultType = dynaset;
}

"The largest fire starts but with the smallest spark." - David Crow

bujji_bec wrote:

delete []p;

bujji_bec wrote:

delete []p; // this statement giving problem

led mike wrote:

it was allocated by whatever clsobj is and therefore should be cleaned up by that same class rather than user code.

Cedric Moonen wrote:

You can allocate memory inside a class a release it outside (in the mean function for example). I agree this is ugly and to be avoided by all means but that won't produce any error.

Cedric Moonen wrote:

In the context of a dll, it's different because your exe and the dll are two separate processes, so the heap managers are different. Everything that has been created by the dll has to be released by your dll and everything that has been created by your exe has to be released by your exe. If you mix that, you will get troubles

led mike wrote:

I have no idea what you mean with that statement. You can't "mix" memory addresses across processes because you don't have access to them. Therefore you can't get that "trouble".