By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,561 Members | 3,127 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,561 IT Pros & Developers. It's quick & easy.

Problem with ODBC open dialogs under Windows 2003

P: n/a
Hello,

I have an application that has been running for years
and had little problem with it. We've been retesting the
latest code under Windows 2003 and found a surprise.

There is a certain case where we allow the MDI app
to close the database and the user can later request
the open dialog. This normally calls the CDatabase
open with the flags that allow the ODBC Open Dialog
boxes to be used. Under Windows 2003 the dialogs
are not happening. No errors are emited from the
code. It appears that perhaps the flags have changed
or some other behavior is occuring. I've not found
an applicable note at Microsoft MSDN or using search
engines. The Jet Driver under Windows 2003 was something
like 2608 and under Windows 2000 we found 2300. I'm
not certain of the versions, so I'll have to post those
tommorow after I get them written down again.

Have you seen a similar behavior change? Was it the
drivers or something else?

Thank you,

David
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On Thu, 7 Apr 2005 01:43:32 UTC, "David" <Fl************@United.Com> wrote:
Hello,

I have an application that has been running for years
and had little problem with it. We've been retesting the
latest code under Windows 2003 and found a surprise.

There is a certain case where we allow the MDI app
to close the database and the user can later request
the open dialog. This normally calls the CDatabase
open with the flags that allow the ODBC Open Dialog
boxes to be used. Under Windows 2003 the dialogs
are not happening. No errors are emited from the
code. It appears that perhaps the flags have changed
or some other behavior is occuring. I've not found
an applicable note at Microsoft MSDN or using search
engines. The Jet Driver under Windows 2003 was something
like 2608 and under Windows 2000 we found 2300. I'm
not certain of the versions, so I'll have to post those
tommorow after I get them written down again.

Have you seen a similar behavior change? Was it the
drivers or something else?

Thank you,

David


Just a follow up for those that might be able to help me.
The ODBC Open Dialogs are what do not appear when the
VC++ v6.0 program calls CDatabase::OpenEx to connect to
the database. The normal parameters are the connect
string and 0. This indicates that the open dialogs are used
when there is a problem with the connect string. We have
other areas of the code that use the parameter to block
the open dialogs. When verifying the parameters to OpenEx
I noticed a parameter that is supposed to force the use
of the open dialogs. That didn't appear to change the
behavior of the application.

What else might be missing from a pristine Windows 2003
installation that differs from a pristine Windows 2000
system? Our application installs the latest MDAC with
the application.

Thank you,

David
Nov 13 '05 #2

P: 1
Hi. We got the same problem (a year later?)
Do you have an idea what is wrong?.I'm not a VC++( C programmer)
and I'm supporting application that use ODBC(VC++) and it worked fine on 2000,but now we testing it in 2003 - and it crashes w'out attempting to connect to DB.
Any suggestions?
Thanks a lot.
Marina
On Thu, 7 Apr 2005 01:43:32 UTC, "David" <FlyLikeAnEagle@United.Com> wrote:
[color=blue]
> Hello,
>
> I have an application that has been running for years
> and had little problem with it. We've been retesting the
> latest code under Windows 2003 and found a surprise.
>
> There is a certain case where we allow the MDI app
> to close the database and the user can later request
> the open dialog. This normally calls the CDatabase
> open with the flags that allow the ODBC Open Dialog
> boxes to be used. Under Windows 2003 the dialogs
> are not happening. No errors are emited from the
> code. It appears that perhaps the flags have changed
> or some other behavior is occuring. I've not found
> an applicable note at Microsoft MSDN or using search
> engines. The Jet Driver under Windows 2003 was something
> like 2608 and under Windows 2000 we found 2300. I'm
> not certain of the versions, so I'll have to post those
> tommorow after I get them written down again.
>
> Have you seen a similar behavior change? Was it the
> drivers or something else?
>
> Thank you,
>
> David[/color]

Just a follow up for those that might be able to help me.
The ODBC Open Dialogs are what do not appear when the
VC++ v6.0 program calls CDatabase::OpenEx to connect to
the database. The normal parameters are the connect
string and 0. This indicates that the open dialogs are used
when there is a problem with the connect string. We have
other areas of the code that use the parameter to block
the open dialogs. When verifying the parameters to OpenEx
I noticed a parameter that is supposed to force the use
of the open dialogs. That didn't appear to change the
behavior of the application.

What else might be missing from a pristine Windows 2003
installation that differs from a pristine Windows 2000
system? Our application installs the latest MDAC with
the application.

Thank you,

David
May 5 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.