Thread: Accessing a database from a dialog.

you can do this one of two ways....

the first is of course.... and it is also the recommend way

MyDialog dlg;


dlg.m_strFName = m_pSet->m_First_Name;
dlg.m_strLName = m_pSet->m_Last_Name;

int iResult = dlg.DoModal();

if( iResult == IDOK )
{
if( dlg.m_strFName != m_pSet->m_FirstName;
....write some code to edit the record set... or add new..

}



the other way is to map.... the variables directly to the dialog

because the record set is being created in your form or in your doc somewhere... you must not create a new one in your dialog, instead create a member variable pointer to the recordset like this...

class MyDialog: publice CDialog
{
...
public:
CMyRecordSet* m_pSet;

//you can also assign the record set in the constructor
void SetRecordSet( CMyRecordSet* pSet){ m_pSet = pSet; }
}


then go to the MFC class wizard the Class Info tab select the proper dialog class int the CLASS NAME drop box... in the foreign class select the derived recordset class... and assign the variable a name like m_pSet... this action will aumatically add the m_pSet variable to your dialog and set it to NULL upon construction....

now whenever you call call MyDialog.... you can update the recordset... through the dialog ..



//assuming that the recordset is open for and is editable

ASSERT( m_pSet->IsOpen() == TRUE )
ASSERT( m_pSet->GetEditMode() != dbEditNone )

CMyDialog dlg( m_pSet ); or CMyDialog dlg; dlg.SetRecordSet( m_pSet );

dlg.DoModal();


this will allow you to map variables directly to the edit and combo controls of your dialog....
This can also create some nasty problems if the recordset is NULL or Closed so make sure it is Open prior to calling dlg.DoModal...

Code:

//** prior to calling this function insure to create the recordset and open it
//** CDaoDatabase db;
//** db.Open( strFullPathAndFileName );
//** m_pSet = new CMyRecordset( &db )
//** m_pSet->Open();
void  CTykeView::CreateTabControl()
{




pSheet = new CPropertySheet( "My Tab", this, 0); 

pSheet->AddPage( &m_Page1 ); 
pSheet->AddPage( &m_Page2 ); 
pSheet->AddPage( &m_Page3 ); 


//***********************************
//** do this prior to creation
//** If you have mapped the RS to the pages
m_page1.SetRecordSetPointer( &m_pSet );
m_page2.SetRecordSetPointer( &m_pSet );
m_page3.SetRecordSetPointer( &m_pSet );

/*
        where the function looks like this
        for each of the property pages
        CMyProPage1::SetRecordSetPointer(CMyRecordset* pSet)
        {
                m_pSet = pSet;
        }

*/

pSheet->Create( this, WS_CHILD | WS_VISIBLE ); 

CRect r; 
m_staticPlaceHolder.GetWindowRect( &r ); 
ScreenToClient( &r ); 

pSheet->SetWindowPos( pSheet, r.top, r.left, 0, 0, SWP_NOSIZE | SWP_NOZORDER ); 


return;
}


to access the pages remember to call pSheet->SetActivePage( n )....otherwise you will get some nasty assertion errors trying to access a non active page... by default the first page is active.. 

and don't forget that prior to editing a recordset you must set edit in the following steps

1. Move to the record
2. call m_pSet->Edit()
3. update the data through the dialog
4. call m_pSet->Update()
5. move to another record or close it...

or
1. m_pSet->AddNew()
2. Update the data m_pSet->m_Name = strName;...etc
3. m_pSet->AddNew()

correction on that

m_pSet->AddNew();
....assign values
m_pSet->Update();

I somehow created a new thread instead of replying look for the new thread....
I sent you a link to a demo I built...
www.vvm.com/~fzamora/DaoDemo.zip

I hope this helps