Suddenly ODBC driver does not work

I have an application that has worked fine for more than 2 years. Suddenly
the users and I get an error message when trying to open the MySql database
for writing. The web host says that I may have a too complicated script or
anything else. So far no help from them.

The page stops and shows "ODBC Drivers error '80040e21'
ODBC driver does not support the requested properties. "

My code here is stopping at the last line:
Dim rsProgr
Set rsProgr = Server.CreateObject("ADODB.Recordset")
rsProgr.Open "Program", objConn, adLockPessimistic, adCmdTable

After many tries with this error message, it suddenly works again as if no
fault has happened. And later, the same story again.
Anyone knows where to start?
/ Rolf

Re: Suddenly ODBC driver does not work

> Re: Suddenly ODBC driver does not work
Well, stop using it!

http://www.aspfaq.com/show.asp?id=2126



--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Re: Suddenly ODBC driver does not work

I really don't know what you suggest with this. My internet provider has
told me to use ODBC with a connection string that is exactly as in the
second example for MySql in the link you gave me. That is also how I did it.

How do you mean that I shall do instead?
/ Rolf




"Bob Barrows [MVP]" skrev i meddelandet
news:OwC5t$68FHA.3876@TK2MSFTNGP09.phx.gbl...
> > Re: Suddenly ODBC driver does not work
> Well, stop using it!
>
> http://www.aspfaq.com/show.asp?id=2126
>
>
>
> --
> Microsoft MVP - ASP/ASP.NET
> Please reply to the newsgroup. This email account is my spam trap so I
> don't check it very often. If you must reply off-line, then remove the
> "NO SPAM"
>
>

Re: Suddenly ODBC driver does not work

I suggest that you either use a native OLE DB connection string as suggested
in my link or ask your ISP for support.
ODBC depends too much on provider-controlled configuration settings.


Rolf Rosenquist wrote:
> I really don't know what you suggest with this. My internet provider
> has told me to use ODBC with a connection string that is exactly as
> in the second example for MySql in the link you gave me. That is also
> how I did it.
>
> How do you mean that I shall do instead?
> / Rolf
>
>
>
>
> "Bob Barrows [MVP]" skrev i meddelandet
> news:OwC5t$68FHA.3876@TK2MSFTNGP09.phx.gbl...
>>> Re: Suddenly ODBC driver does not work
>> Well, stop using it!
>>
>> http://www.aspfaq.com/show.asp?id=2126
>>
>>
>>
>> --
>> Microsoft MVP - ASP/ASP.NET
>> Please reply to the newsgroup. This email account is my spam trap so
>> I don't check it very often. If you must reply off-line, then remove
>> the "NO SPAM"

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Re: Suddenly ODBC driver does not work

Rolf Rosenquist wrote:
> I have an application that has worked fine for more than 2 years.
> Suddenly the users and I get an error message when trying to open the
> MySql database for writing. The web host says that I may have a too
> complicated script or anything else. So far no help from them.
>
> The page stops and shows "ODBC Drivers error '80040e21'
> ODBC driver does not support the requested properties. "
>
> My code here is stopping at the last line:
> Dim rsProgr
> Set rsProgr = Server.CreateObject("ADODB.Recordset")
> rsProgr.Open "Program", objConn, adLockPessimistic, adCmdTable
>
> After many tries with this error message, it suddenly works again as
> if no fault has happened. And later, the same story again.
> Anyone knows where to start?
> / Rolf

I just noticed that you are using MySQL. I have no experience with that
database, but I have to ask, why are you using a pessimistic lock? And why
the adCmdTable? Could you not specify a sql statement that returns exactly
the columns and rows that you need and use a default forward-only cursor?

If you are planning to make data updates, you should be using DML
(UPDATE/INSERT/DELETE statements) rather than resource- and lock-intensive
cursors (recordsets). You can use transactions with MySQL, so there is no
need for pessimistic locking.

I suspect your provider needs to install a new version of the MySQL ODBC
driver if you intend to continue using these inefficient techniques. In any
event, you will likely get better suport by going to a MySQL forum or
newsgroup if any exist.

Bob Barrows

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Re: Suddenly ODBC driver does not work

Bob with MySQL on a windows server your pretty much going to be using MyODBC
(now called Connector/ODBC)


"Bob Barrows [MVP]" wrote in message
news:%23lGm89A9FHA.1248@TK2MSFTNGP14.phx.gbl...
> Rolf Rosenquist wrote:
>> I have an application that has worked fine for more than 2 years.
>> Suddenly the users and I get an error message when trying to open the
>> MySql database for writing. The web host says that I may have a too
>> complicated script or anything else. So far no help from them.
>>
>> The page stops and shows "ODBC Drivers error '80040e21'
>> ODBC driver does not support the requested properties. "
>>
>> My code here is stopping at the last line:
>> Dim rsProgr
>> Set rsProgr = Server.CreateObject("ADODB.Recordset")
>> rsProgr.Open "Program", objConn, adLockPessimistic, adCmdTable
>>
>> After many tries with this error message, it suddenly works again as
>> if no fault has happened. And later, the same story again.
>> Anyone knows where to start?
>> / Rolf
>
> I just noticed that you are using MySQL. I have no experience with that
> database, but I have to ask, why are you using a pessimistic lock? And why
> the adCmdTable? Could you not specify a sql statement that returns exactly
> the columns and rows that you need and use a default forward-only cursor?
>
> If you are planning to make data updates, you should be using DML
> (UPDATE/INSERT/DELETE statements) rather than resource- and lock-intensive
> cursors (recordsets). You can use transactions with MySQL, so there is no
> need for pessimistic locking.
>
> I suspect your provider needs to install a new version of the MySQL ODBC
> driver if you intend to continue using these inefficient techniques. In
> any event, you will likely get better suport by going to a MySQL forum or
> newsgroup if any exist.
>
> Bob Barrows
>
> --
> Microsoft MVP - ASP/ASP.NET
> Please reply to the newsgroup. This email account is my spam trap so I
> don't check it very often. If you must reply off-line, then remove the
> "NO SPAM"
>