C / C++ / MFC Discussion Boards

pjmvn13-Mar-06 13:39

13-Mar-06 13:39

See this code:

try<br />
{<br />
conn = new CDaoDatabase();		<br />
conn->Open(fileName);<br />
}<br />
catch(CDaoException* error){}

This code will open the Database for me but i can not catch the CDaoException when error. Ex: when the fileName is wrong.

Please help me for this problem.

Thanks

Re: Can not catch CDaoException

Hamid_RT13-Mar-06 17:20

Hamid_RT

13-Mar-06 17:20

Hi pjmvn,

try
{
CDaoDatabase *conn;
LPCTSTR fileName="c:\1";
conn = new CDaoDatabase();
conn->Open(fileName);
}

catch(CDaoException* error)
{
switch( )
{
case 1://Here is error code 1 is example
break;
}
}

-- modified at 23:32 Monday 13th March, 2006

Re: Can not catch CDaoException

pjmvn13-Mar-06 19:19

pjmvn

13-Mar-06 19:19

Sorry, my question is not abvious.
This is my code:

try<br />
{<br />
conn = new CDaoDatabase();		<br />
conn->Open(fileName);<br />
}<br />
catch(CDaoException* error)<br />
{<br />
delete conn;<br />
conn = NULL;<br />
LPTSTR errors = L"";<br />
error->GetErrorMessage(errors,100,NULL);<br />
AfxMessageBox(errors);<br />
}

When fileName is wrong. The program does not show Message.
It debug only

debugging

cuteee13-Mar-06 11:31

cuteee

13-Mar-06 11:31

I put a breakpoint at a location and was trying to debug the program. When i hit "run" it should stop at the breakpoint. But, it is giving me a message that "the code has exited" without stopping at the breakpoint. I tried changing the location. Wherever in the program i put a breakpoint and try to debug, the same thing is happening. What might be the problem?

Re: debugging

Stephen Hewitt13-Mar-06 11:46

Stephen Hewitt

13-Mar-06 11:46

Sound like the breakpoint isn't being hit. Put a call the MessageBox in the code to verify this suspicion.

Steve

Re: debugging

David Crow13-Mar-06 14:46

David Crow

13-Mar-06 14:46

cuteee wrote:
When i hit "run"...

Is this via F5 or Ctrl+F5?

"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain

"There is no death, only a change of worlds." - Native American Proverb

Re: debugging

MANISH RASTOGI13-Mar-06 17:19

MANISH RASTOGI

13-Mar-06 17:19

Re: debugging

David Crow14-Mar-06 2:29

David Crow

14-Mar-06 2:29

So even though the breakpoint is not being hit, does the code in that routine execute?

"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain

"There is no death, only a change of worlds." - Native American Proverb

Close modeless dialog during OnInitDialog()

Doug Allen13-Mar-06 11:03

Doug Allen

13-Mar-06 11:03

Hi,

I am wondering what the correct way is to properly end a modeless dialog during the OnInitDialog. I currently have 2 (lets call them A and B) dialogs, B is called during the OnInitDialog handling of A. If the return from B is false, then I don't want to display A. When the dialog was modal, I just used an EndDialog(IDABORT) call without any problems. Now that I moved to modeless, I'm wondering if this is still correct. I can't seem to find anywhere that this topic is discussed. Thanks for the help.

Doug

Re: Close modeless dialog during OnInitDialog()

Michael Dunn13-Mar-06 11:12

Michael Dunn

13-Mar-06 11:12

Use DestroyWindow() to close a modeless dialog.

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | NEW!! PimpFish | CP SearchBar v3.0 | C++ Forum FAQ

Re: Close modeless dialog during OnInitDialog()

Doug Allen13-Mar-06 11:35

Doug Allen

13-Mar-06 11:35

Mike,

This doesn't seem correct since the dialog hasn't been created yet. I agree that typically you use the DestroyWindow() function to close the dialog, but I have created the dialog yet through the OnInitDialog().

Thanks,
Doug

Re: Close modeless dialog during OnInitDialog()

Stephen Hewitt13-Mar-06 11:47

Stephen Hewitt

13-Mar-06 11:47

Inside OnInitDialog the dialog has been created - It's just not visible yet.

Steve

Re: Close modeless dialog during OnInitDialog()

Doug Allen13-Mar-06 11:57

Doug Allen

13-Mar-06 11:57

Ok - I get some assertion errors if I use the destroywindow() call (line 207 of winocc.cpp and line 105 of afxwin2.inl). If I use the EndDialog(IDABORT), even though this is a modeless dialog, I don't get these assertion errors. Are you sure that the above statements are true?

Re: Close modeless dialog during OnInitDialog()

Stephen Hewitt13-Mar-06 12:39

Stephen Hewitt

13-Mar-06 12:39

Verify it for yourself (I would). Put a breakpoint in OnInitDialog and when hit look at the this->m_hWnd class member. You can use Spy (or code is a call to ::IsWindow) to verify the HWND exists. But yes, I'm sure.

Steve

Re: Close modeless dialog during OnInitDialog()

Doug Allen13-Mar-06 12:53

Doug Allen

13-Mar-06 12:53

Ok, that seems to be true that the handle is there. However, when you call destroy window, the handle gets removed (which I believe is what is causing the assertion errors). It would seem that we don't want to Destroy the window yet. Does this make sense?

Thanks,
Doug

Re: Close modeless dialog during OnInitDialog()

Stephen Hewitt13-Mar-06 12:56

Stephen Hewitt

13-Mar-06 12:56

Sounds possible - But I don't know off hand. The lines numbers in my MFC don't line up with yours (I use MSVC6) so I can't have a look and see what the problem is. Can you post some details of the ASSERTS?

Steve

Re: Close modeless dialog during OnInitDialog()

Doug Allen13-Mar-06 13:06

Doug Allen

13-Mar-06 13:06

Steve,
Both assertion errors are related to the handle being null (line 207 of winocc.cpp - ASSERT(::IsWindow(m_hWnd) || (m_pCtrlSite != NULL)); and line 105 of afxwin2.inl - { ASSERT(::IsWindow(m_hWnd)); ::GetWindowRect(m_hWnd, lpRect); }). This means the handle shouldn't be null - caused by the destroywindow(). So, what is the correct call for the closing modeless during OnInitDIalog()?

Thanks,
Doug

Re: Close modeless dialog during OnInitDialog()

Stephen Hewitt13-Mar-06 13:09

Stephen Hewitt

13-Mar-06 13:09

Try this:

PostMessage(WM_CLOSE);

Steve

Re: Close modeless dialog during OnInitDialog()

Doug Allen13-Mar-06 13:15

Doug Allen

13-Mar-06 13:15

Nope

Re: Close modeless dialog during OnInitDialog()

Stephen Hewitt13-Mar-06 16:04

Stephen Hewitt

13-Mar-06 16:04

Ok try this:

::PostMessage(m_hWnd, WM_CLOSE, 0, 0);

Steve

Re: Close modeless dialog during OnInitDialog()

Doug Allen14-Mar-06 2:34

Doug Allen

14-Mar-06 2:34

Nope

Re: Close modeless dialog during OnInitDialog()

Stephen Hewitt14-Mar-06 17:42

Stephen Hewitt

14-Mar-06 17:42

I tested this last one on a wizard generated MFC application and it worked. Are you handling the WM_CLOSE message or something?

Steve

Re: Close modeless dialog during OnInitDialog()

Doug Allen15-Mar-06 2:53

Doug Allen

15-Mar-06 2:53

Steve,

Yes I am using WM_CLOSE message handling. After I disabled the WM_CLOSE message handler, I get a better result, but still not what I wanted. When I use the statement you provided without the WM_CLOSE, I still can see the dialog open and then close (although briefly). If I use the EndDialog(IDABORT) call, I never see this quick display of the window (desired effect).

Thanks,
Doug

Re: Close modeless dialog during OnInitDialog()

Ryan Binns13-Mar-06 17:13

Ryan Binns

13-Mar-06 17:13

Doug Allen wrote:
I get some assertion errors if I use the destroywindow()

Are the assertion errors appearing during the DestroyWindow call or after it?

Ryan

"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"

Re: Close modeless dialog during OnInitDialog()

Doug Allen14-Mar-06 2:44

Doug Allen

14-Mar-06 2:44

Ryan,

From the earlier posts, you cn see that the assertion errors are caused after the DestroyWindow() is called due to m_HWnd being null. It doesn't seem right that you would call DestroyWindow() before the dialog is shown.

Thanks,
Doug

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.