Oh, I see. I've just checked the "Change Bit Integer Columns to Int" in the
ODBC Properties and have had no problems. Then again, I don't need the Big
Integer Data Type.
Lee
Hello, Lee,
I don't think the problem I'm having has anything to do with the ODBC
driver, because I used the same MyODBC driver under Windows 98, and I had no
problems whatsoever. Yes, I'm using ADO -- that explains why Access still
works. Somehow, there's some ADO functionality in Windows ME and 2000 that
does not recognize BIGINT datatypes. It can't be anything in VB, since in
both cases I'm using VB 6.0 with service pak 4. Only thing that changed was
the O/S from Win 98 to Windows ME and Windows 2000. Everything else was the
same, same version MyODBC, same VB 6.0 sp4, same VB application / VB code.
I've actually had little trouble with MyODBC and ADO -- except for earlier
versions of MyODBC.
Thanks,
Laszlo
- Original Message -
From: "Lee Jenkins" [EMAIL PROTECTED]
To: "MySQL Mail list" [EMAIL PROTECTED]
Sent: Wednesday, January 17, 2001 3:30 PM
Subject: RE: Windows ME / 2000 VB problem with BIGINT data type
With your VB App, are you using DAO or ADO? MS Access uses DAO to working
with ODBC while VB apps using ADO have problems with the MyODBC driver (at
least with me it did). I recently changed much code in my VB app to work
with MySQL from DAO to ADO. However, many methods aren't supported like
the
UPDATE method of the RS object. Data Bound controls also stick their
noses
up at the MyODBC driver.
Lee
-Original Message-
From: Laszlo G. Szijarto [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 17, 2001 2:41 PM
To: Quentin Bennett; [EMAIL PROTECTED]
Subject: Re: Windows ME / 2000 VB problem with BIGINT data type
Thank you, Quentin,
Hey, does anyone know where the problem lies here? Where in Windows ME /
2000? Why does Access still import OK? Is there something that needs to
be
done with MyODBC to handle BIGINT types in the future?
Thank you,
Laszlo
- Original Message -
From: "Quentin Bennett" [EMAIL PROTECTED]
To: "'Laszlo G. Szijarto'" [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, January 17, 2001 2:30 PM
Subject: RE: Windows ME / 2000 VB problem with BIGINT data type
Hi,
Don't you love M$.
ALTER TABLE CHANGE COLUMN myname myname INTEGER;
Regards
Quentin
-Original Message-
From: Laszlo G. Szijarto [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 18 January 2001 08:28
To: Laszlo G. Szijarto; [EMAIL PROTECTED]
Subject: Re: Windows ME / 2000 VB problem with BIGINT data type
I isolated the problem because if I do a
"select * from table" -- I get the error.
but if I do "select field1, field3, field4 from table", where I leave
out
the BIGINT column, I'm fine.
and when I do a "select field2 form table" where field2 is the BIGINT
column, I get the same error
finally, I created a new table, with the definitions being all the same
except that I replaced BIGINT columns with INT columns -- and everything
worked properly. Is there and ALTER table statement in SQL that will
change
data type definitions -- ps, all my data will currently fit into the INT
size type. I think I was a bit ambition in first defining the tables.
Thank you,
Laszlo Szijarto
- Original Message -
From: "Laszlo G. Szijarto" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, January 17, 2001 2:22 PM
Subject: Windows ME / 2000 VB problem with BIGINT data type
I wrote to the list earlier on the above problem. I had a VB app that
accessed a mysql (on Linux) table through MyODBC. Apparently the
problem
is
that the new ODBC connection providers in Windows ME / 2000 do not like
the
BIGINT datatype. Yet, strangely, MS Access 97 can import the data from
said
table just fine (in Windows ME and 2000). And the VB app worked just
fine
on Windows 98. Can someone offer insight into this problem? What could
be
going on here? Also, if possible, does someone know the SQL syntax for
changing the datatype of an existing column from BIGINT to INT. Thank
you
very much,
Laszlo Szijarto
- Original Message -
From: "Laszlo G. Szijarto" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, January 17, 2001 2:22 PM
Subject: Windows ME / 2000 VB problem with BIGINT data type
I wrote to the list earlier on the above problem. I had a VB app that
accessed a mysql (on Linux) table through MyODBC. Apparently the
problem
is
that the new ODBC connection providers in Windows ME / 2000 do not like
the
BIGINT datatype. Yet, strangely, MS Access 97 can import the data from
said
table just fine (in Windows ME and 2000). And the VB app worked just
fine
on Windows 98. Can someone offer insight into this problem? What could
be
going on here? A
