ODBC drivers not listed in SS2005 import wizard

I'm trying to import an RBASE table into SQL Server 2005. In 2000, the RBAS
E
ODBC driver was listed in the drop down list of the import wizard. It is no
t
listed in the 2005 wizard. Is there a fix for this?
Thanks,
MikeTry using the .Net Framework Data Provider for ODBC.
Then enter the DSN or the driver and connection string.
-Sue
On Fri, 26 May 2006 13:29:02 -0700, Mike
<Mike@.discussions.microsoft.com> wrote:

>I'm trying to import an RBASE table into SQL Server 2005. In 2000, the RBA
SE
>ODBC driver was listed in the drop down list of the import wizard. It is n
ot
>listed in the 2005 wizard. Is there a fix for this?
>Thanks,
> Mike|||Thanks Sue...I'll give that a try!
"Sue Hoegemeier" wrote:

> Try using the .Net Framework Data Provider for ODBC.
> Then enter the DSN or the driver and connection string.
> -Sue
> On Fri, 26 May 2006 13:29:02 -0700, Mike
> <Mike@.discussions.microsoft.com> wrote:
>
>

ODBC drivers needed

My server is running with 2003R2 x64 with SQL 2005. Some of my client
computers are having some issues with ODBC errors while working in an
accounting package. I have been told that it is most likely a driver
compatibility issue between the XP pro versions on the clients and the 64
bit version on my server.
I suppose first does this seem plausible, and where might I find the updated
drivers for XP? I am not sure if this is the correct forum for this request,
but it seemed to be the closest.
Many thanks in advance.
David
David (David@.Fidia.com) writes:
> My server is running with 2003R2 x64 with SQL 2005. Some of my client
> computers are having some issues with ODBC errors while working in an
> accounting package. I have been told that it is most likely a driver
> compatibility issue between the XP pro versions on the clients and the 64
> bit version on my server.
> I suppose first does this seem plausible, and where might I find the
> updated drivers for XP? I am not sure if this is the correct forum for
> this request, but it seemed to be the closest.
http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-a9e0-3a1afbd5922e&DisplayLang=en
and
[url]http://www.microsoft.com/downloads/info.aspx?na=22&p=4&SrcDisplayLang=en&SrcCategoryI d=&SrcFamilyId=&u=%2fdownloads%2fdetails.aspx%3fFa milyID%3d7358da31-959c-4e3e-8115-51dc6d441365%26DisplayLang%3den[/url]
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

ODBC drivers for sql server 2005, 64 bit

Hi,
I have a client server app that connects to sql server through ODBC, it
works fine when connecting to sql server 2005 32 bit, but when connecting to
sql server 64 bit from the client on Windows XP it behaves strangely, are
there separate set of odbc drivers that one has to use to connect to sql
server 2005 64 bit, even from 32 bit machine.
Thank you
VadimIt should be transparent to remote clients that the SQL Server is 64-bit.
The same client drivers can be used to connect to a 32 or 64-bit server.
Hope this helps.
Dan Guzman
SQL Server MVP
"Vadim" <vadim@.dontsend.com> wrote in message
news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have a client server app that connects to sql server through ODBC, it
> works fine when connecting to sql server 2005 32 bit, but when connecting
> to sql server 64 bit from the client on Windows XP it behaves strangely,
> are there separate set of odbc drivers that one has to use to connect to
> sql server 2005 64 bit, even from 32 bit machine.
> Thank you
> Vadim
>|||Thank you, Dan
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:452AD768-B04F-4CD1-A54B-0C15E260ED3A@.microsoft.com...
> It should be transparent to remote clients that the SQL Server is 64-bit.
> The same client drivers can be used to connect to a 32 or 64-bit server.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vadim" <vadim@.dontsend.com> wrote in message
> news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
>

ODBC drivers for sql server 2005, 64 bit

Hi,
I have a client server app that connects to sql server through ODBC, it
works fine when connecting to sql server 2005 32 bit, but when connecting to
sql server 64 bit from the client on windows xp it behaves strangely, are
there separate set of odbc drivers that one has to use to connect to sql
server 2005 64 bit, even from 32 bit machine.
Thank you
Vadim
It should be transparent to remote clients that the SQL Server is 64-bit.
The same client drivers can be used to connect to a 32 or 64-bit server.
Hope this helps.
Dan Guzman
SQL Server MVP
"Vadim" <vadim@.dontsend.com> wrote in message
news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have a client server app that connects to sql server through ODBC, it
> works fine when connecting to sql server 2005 32 bit, but when connecting
> to sql server 64 bit from the client on windows xp it behaves strangely,
> are there separate set of odbc drivers that one has to use to connect to
> sql server 2005 64 bit, even from 32 bit machine.
> Thank you
> Vadim
>
|||Thank you, Dan
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:452AD768-B04F-4CD1-A54B-0C15E260ED3A@.microsoft.com...
> It should be transparent to remote clients that the SQL Server is 64-bit.
> The same client drivers can be used to connect to a 32 or 64-bit server.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vadim" <vadim@.dontsend.com> wrote in message
> news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
>

ODBC drivers for sql server 2005, 64 bit

Hi,
I have a client server app that connects to sql server through ODBC, it
works fine when connecting to sql server 2005 32 bit, but when connecting to
sql server 64 bit from the client on windows xp it behaves strangely, are
there separate set of odbc drivers that one has to use to connect to sql
server 2005 64 bit, even from 32 bit machine.
Thank you
VadimIt should be transparent to remote clients that the SQL Server is 64-bit.
The same client drivers can be used to connect to a 32 or 64-bit server.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Vadim" <vadim@.dontsend.com> wrote in message
news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
> Hi,
> I have a client server app that connects to sql server through ODBC, it
> works fine when connecting to sql server 2005 32 bit, but when connecting
> to sql server 64 bit from the client on windows xp it behaves strangely,
> are there separate set of odbc drivers that one has to use to connect to
> sql server 2005 64 bit, even from 32 bit machine.
> Thank you
> Vadim
>|||Thank you, Dan
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:452AD768-B04F-4CD1-A54B-0C15E260ED3A@.microsoft.com...
> It should be transparent to remote clients that the SQL Server is 64-bit.
> The same client drivers can be used to connect to a 32 or 64-bit server.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Vadim" <vadim@.dontsend.com> wrote in message
> news:%23MyV57ECHHA.5068@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> I have a client server app that connects to sql server through ODBC, it
>> works fine when connecting to sql server 2005 32 bit, but when connecting
>> to sql server 64 bit from the client on windows xp it behaves strangely,
>> are there separate set of odbc drivers that one has to use to connect to
>> sql server 2005 64 bit, even from 32 bit machine.
>> Thank you
>> Vadim
>sql

odbc drivers for btrieve for sql

Does anyone know where I can find odbc drivers so I can cannect to a btrieve
database from sql 2000? Are there native sql 2000 drivers that support
this?
Thanks,
Jim'BTrieve' is now 'Pervasive'
http://www.pervasive.com/integratio...odbcvendors.asp
"Jims" <biz@.neocasa.net> wrote in message
news:#KtFZX4XEHA.3420@.TK2MSFTNGP12.phx.gbl...
> Does anyone know where I can find odbc drivers so I can cannect to a
btrieve
> database from sql 2000? Are there native sql 2000 drivers that support
> this?
> Thanks,
> Jim
>

odbc drivers for btrieve for sql

Does anyone know where I can find odbc drivers so I can cannect to a btrieve
database from sql 2000? Are there native sql 2000 drivers that support
this?
Thanks,
Jim
'BTrieve' is now 'Pervasive'
http://www.pervasive.com/integration...dbcvendors.asp
"Jims" <biz@.neocasa.net> wrote in message
news:#KtFZX4XEHA.3420@.TK2MSFTNGP12.phx.gbl...
> Does anyone know where I can find odbc drivers so I can cannect to a
btrieve
> database from sql 2000? Are there native sql 2000 drivers that support
> this?
> Thanks,
> Jim
>

odbc drivers for btrieve for sql

Does anyone know where I can find odbc drivers so I can cannect to a btrieve
database from sql 2000? Are there native sql 2000 drivers that support
this?
Thanks,
Jim'BTrieve' is now 'Pervasive'
http://www.pervasive.com/integration/support/odbcvendors.asp
"Jims" <biz@.neocasa.net> wrote in message
news:#KtFZX4XEHA.3420@.TK2MSFTNGP12.phx.gbl...
> Does anyone know where I can find odbc drivers so I can cannect to a
btrieve
> database from sql 2000? Are there native sql 2000 drivers that support
> this?
> Thanks,
> Jim
>

ODBC drivers errro '80040e14'

Hi Sir/Madam,
I have a error from my ASP, SQL application as :
Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot sort a row
of size
8162, which is greater than the allowable maximum of 8094.
The SQL query in ASP code as:
SQL = "select * from Entry,Entrant where Entry.EntrantID=Entrant.EntrantID
and entry.Competition = 'MADC2004' order by CatID asc"
As long as I remove the 'order by CatID asc', the error gone. I don't
understand why the 'order by CatID' will cause the error. But I need to sort
the result.
Please help.....
Thank you very much
Ben LI'm guessing that the rows of your result set, since they come from two
tables, total more than 8094 bytes. Certainly you don't need to see
every column of each table, since at the least, you only need to display
EntrantID once, and if you can live with results without all the
columns, you may solve the problem. It's also possible that you really
don't ever have 8094+ bytes in any one row - this could be the case if
you have char or nchar columns where you might be fine with varchar or
nvarchar.
SK
B L wrote:

>Hi Sir/Madam,
>I have a error from my ASP, SQL application as :
>Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
>[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot sort a ro
w of size
>8162, which is greater than the allowable maximum of 8094.
>The SQL query in ASP code as:
>SQL = "select * from Entry,Entrant where Entry.EntrantID=Entrant.EntrantID
>and entry.Competition = 'MADC2004' order by CatID asc"
>As long as I remove the 'order by CatID asc', the error gone. I don't
>understand why the 'order by CatID' will cause the error. But I need to sor
t
>the result.
>Please help.....
>Thank you very much
>Ben L
>
>
>
>
>
>
>|||Hi Steve,
I selected less column and the query working now. Thank you very much for
the information.
Regards
Ben
"Steve Kass" <skass@.drew.edu> wrote in message
news:%23jGFhDZBEHA.3804@.TK2MSFTNGP09.phx.gbl...
> I'm guessing that the rows of your result set, since they come from two
> tables, total more than 8094 bytes. Certainly you don't need to see
> every column of each table, since at the least, you only need to display
> EntrantID once, and if you can live with results without all the
> columns, you may solve the problem. It's also possible that you really
> don't ever have 8094+ bytes in any one row - this could be the case if
> you have char or nchar columns where you might be fine with varchar or
> nvarchar.
> SK
> B L wrote:
>
Entry.EntrantID=Entrant.EntrantID
sort
>

ODBC Drivers error '80040e31'

We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely apprec
iated?
Any help would be greatly appreciated.
Thank you.
- A l p e rMaybe some information here:
http://www.aspfaq.com/2287
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:3F1AC249-81D0-498F-AB81-E8F628A1F98C@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> If anyone has any ideas as to possible reasons, it would be immensely
appreciated?
> Any help would be greatly appreciated.
> Thank you.
> - A l p e r
>|||Thanks Aaron!
I've changed the connection string and am connecting with OLE DB provider no
w...we'll see if it makes any difference...
But I have a feeling it will start throwing time outs any way... May be our
tables, queries, etc. need to be optimized...
Thanks,
- A l p e r
-- Aaron Bertrand - MVP wrote: --
Maybe some information here:
http://www.aspfaq.com/2287
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:3F1AC249-81D0-498F-AB81-E8F628A1F98C@.microsoft.com...
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
appreciated?[vbcol=seagreen]
>sql

ODBC Drivers error '80040e31'

We moved our SQL Server 2000 onto a Win 2003 box (with SQL
SP3a applied).
Lately, we have been experiencing intermittent ADO
timeouts on our webpages displaying the following error:
Microsoft OLE DB Provider for ODBC Drivers
error '80040e31'
[Microsoft][ODBC SQL Server Driver]Timeout expired
If anyone has any ideas as to possible reasons, it would be immensely appreciated?
Any help would be greatly appreciated.
Thank you.
- A l p e r
Maybe some information here:
http://www.aspfaq.com/2287
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:3F1AC249-81D0-498F-AB81-E8F628A1F98C@.microsoft.com...
> We moved our SQL Server 2000 onto a Win 2003 box (with SQL
> SP3a applied).
> Lately, we have been experiencing intermittent ADO
> timeouts on our webpages displaying the following error:
> Microsoft OLE DB Provider for ODBC Drivers
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
> If anyone has any ideas as to possible reasons, it would be immensely
appreciated?
> Any help would be greatly appreciated.
> Thank you.
> - A l p e r
>
|||Thanks Aaron!
I've changed the connection string and am connecting with OLE DB provider now...we'll see if it makes any difference...
But I have a feeling it will start throwing time outs any way... May be our tables, queries, etc. need to be optimized...
Thanks,
- A l p e r
-- Aaron Bertrand - MVP wrote: --
Maybe some information here:
http://www.aspfaq.com/2287
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Alper" <anonymous@.discussions.microsoft.com> wrote in message
news:3F1AC249-81D0-498F-AB81-E8F628A1F98C@.microsoft.com...[vbcol=seagreen]
> SP3a applied).
> timeouts on our webpages displaying the following error:
> error '80040e31'
> [Microsoft][ODBC SQL Server Driver]Timeout expired
appreciated?
>

ODBC Drivers error '80004005'

Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
that accessed a SQL server 2000 running on windows 2003 through DSN. Every
once in a while the webpage becomes inaccessable and gives the following
message:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][DBNETLIB] General network error.
Check your network documentation.
/direct/dbConn.asp, line 34
Line 34 of the asp file contains the line:
adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
The webpage doesn't just comeback after a few minutes but instead stays
inaccessible until the SQL Server is restarted.
The only way around this problem has been to restart the SQL server every 3
hours in order to decrease the webserver downtime.
Please help,
Danny
It looks like an upgrade to SQL Server 2000 Service Pack 4 solved the
problem.
Dannyb
"Dannyb" <dannyb@.alianza.com> wrote in message
news:uPpKjQqNGHA.740@.TK2MSFTNGP12.phx.gbl...
> Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
> that accessed a SQL server 2000 running on windows 2003 through DSN.
> Every
> once in a while the webpage becomes inaccessable and gives the following
> message:
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][DBNETLIB] General network error.
> Check your network documentation.
> /direct/dbConn.asp, line 34
> Line 34 of the asp file contains the line:
> adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
> The webpage doesn't just comeback after a few minutes but instead stays
> inaccessible until the SQL Server is restarted.
> The only way around this problem has been to restart the SQL server every
> 3
> hours in order to decrease the webserver downtime.
> Please help,
> Danny
>
>

ODBC Drivers error '80004005'

Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
that accessed a SQL server 2000 running on windows 2003 through DSN. Every
once in a while the webpage becomes inaccessable and gives the following
message:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][DBNETLIB] General network er
ror.
Check your network documentation.
/direct/dbConn.asp, line 34
Line 34 of the asp file contains the line:
adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
The webpage doesn't just comeback after a few minutes but instead stays
inaccessible until the SQL Server is restarted.
The only way around this problem has been to restart the SQL server every 3
hours in order to decrease the webserver downtime.
Please help,
DannyIt looks like an upgrade to SQL Server 2000 Service Pack 4 solved the
problem.
Dannyb
"Dannyb" <dannyb@.alianza.com> wrote in message
news:uPpKjQqNGHA.740@.TK2MSFTNGP12.phx.gbl...
> Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
> that accessed a SQL server 2000 running on windows 2003 through DSN.
> Every
> once in a while the webpage becomes inaccessable and gives the following
> message:
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][DBNETLIB] General netwo
rk error.
> Check your network documentation.
> /direct/dbConn.asp, line 34
> Line 34 of the asp file contains the line:
> adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
> The webpage doesn't just comeback after a few minutes but instead stays
> inaccessible until the SQL Server is restarted.
> The only way around this problem has been to restart the SQL server every
> 3
> hours in order to decrease the webserver downtime.
> Please help,
> Danny
>
>

ODBC drivers

After I installated Service Pack 4 on SQL 2000, suddenly all my ODBC
drivers
dissapered.
How I can get them back?
Did you try reinstalling MDAC or using component checker to
verify your MDAC installation? Component checker and MDAC
versions can be downloaded from:
http://msdn.microsoft.com/data/mdac/...s/default.aspx
-Sue
On Fri, 23 Sep 2005 09:37:47 +0300, "news.infonet.ee"
<news@.news.no.spam.ee> wrote:

>After I installated Service Pack 4 on SQL 2000, suddenly all my ODBC
>drivers
>dissapered.
>How I can get them back?
>

ODBC drivers

Hi
On our SQL 2000 Std server, when creating a ODBC there are no drivers to
chose from (i.e SQL DSN etc). Even when installing addtional SQL instance
we get a Cannot find default Data Source message)
I have tried reinstalling MDAC 2.7 but the ODBC drivers does not appear in
the drivers tabs in ODBC admin tool.
I am stuck to why this is happening. Any help/advice to resolve this
strange problem.
p.s i can use Enterprise Manager from my working station to connect to the
SQL server ( but not on the server itself)
Regards
James DownesI have solved the problem. I imported the ODBC registry keys from a working
ODBC server.
Regards
Z
"Zenduce" <james@.zenduce.net> wrote in message
news:#EFueg4SDHA.1916@.TK2MSFTNGP12.phx.gbl...
> Hi
> On our SQL 2000 Std server, when creating a ODBC there are no drivers to
> chose from (i.e SQL DSN etc). Even when installing addtional SQL
instance
> we get a Cannot find default Data Source message)
> I have tried reinstalling MDAC 2.7 but the ODBC drivers does not appear
in
> the drivers tabs in ODBC admin tool.
> I am stuck to why this is happening. Any help/advice to resolve this
> strange problem.
> p.s i can use Enterprise Manager from my working station to connect to
the
> SQL server ( but not on the server itself)
> Regards
> James Downes
>sql

ODBC drivers

After I installated Service Pack 4 on SQL 2000, suddenly all my ODBC
drivers
dissapered.
How I can get them back?Did you try reinstalling MDAC or using component checker to
verify your MDAC installation? Component checker and MDAC
versions can be downloaded from:
http://msdn.microsoft.com/data/mdac...ds/default.aspx
-Sue
On Fri, 23 Sep 2005 09:37:47 +0300, "news.infonet.ee"
<news@.news.no.spam.ee> wrote:

>After I installated Service Pack 4 on SQL 2000, suddenly all my ODBC
>drivers
>dissapered.
>How I can get them back?
>

ODBC Components not loading

I am running SQL Express on a Server 2003 R2 machine. The application that uses the database needs to have the ODBC drivers installed. Everytime I try to add them, the installer looks like it does something, but when I go to the Data Source option under Administrative Tools, the only driver I see is the SQL Native Client. Any ideas?1) What ODBC driver are you expecting to install?
2) When you mentioned "Data Source", you meant that the drivers did not show up under the "drivers" tab of "ODBC Data Source Administrator", correct?|||

The SQL Native client is the ODBC driver for SQL Server. You just need to add a new DSN to connect to the right server and then use the DSN to connect. If that is not what you intend on doing, please describe exactly what you trying to do.

The following links talks more about it in detail.

http://blogs.msdn.com/sqlnativeclient/archive/2006/09/27/774287.aspx

HTH

Riyaz