Showing posts with label installed. Show all posts
Showing posts with label installed. Show all posts

Friday, March 30, 2012

Odbc error

Dear all
My one user has installed sql server 2000 enterprise edition , SP3
(8.00.0860) on my computer.
I have created one odbc connection to sql server.
When he want to connect to sql user via odbc in application he gets
following error
Statement(s) could not be prepared
Unable to close cursor
[Microsoft][ODBC SQL Server Driver]Invalid cursor stat
What can be the problem?
RegardsWhat language is the application written in? At least the failing module?
I have seen similar errors in both T/SQL (implying a Stored Procedure) and C
(api level calls) modules.
I suspect it needs to be relinked with your new modules. To me, it sounds
like the api calls either are for a different ODBC release or have messed up
pointers.
If you can supply error numbers and complete error messages, it woulld help
--
Joseph R.P. Maloney, CSP,CCP,CDP
"amish" wrote:
> Dear all
> My one user has installed sql server 2000 enterprise edition , SP3
> (8.00.0860) on my computer.
> I have created one odbc connection to sql server.
> When he want to connect to sql user via odbc in application he gets
> following error
> Statement(s) could not be prepared
> Unable to close cursor
> [Microsoft][ODBC SQL Server Driver]Invalid cursor stat
> What can be the problem?
> Regards
>

ODBC Error

I'm getting an error message I've never seen before when I installed my
application on a client's machine.
I've got seven machines at this location that all work fine, when I install
on a new machine, I can connect through ODBC Administrator; but, when I try
to connect through the program I get this error message:
[ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
[ODBC SQL Server Driver][TCP/IP
Sockets]ConnectionOpen(SECDoClientHandsh
ake()).
I've looked on KB and have not been able to find anything specific on this
problem.
Any ideas?
Thanks in advance.This might be the same issue reported in the KB article at the link
http://support.microsoft.com/defaul...b;en-us;Q322144
Regards,
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Uwa Agbonile[MSFT]
"Dennis Powell" <dennis.powell@.monroe.XXXXXXXXX> wrote in message
news:OA6%23L0fYFHA.2128@.TK2MSFTNGP15.phx.gbl...
> I'm getting an error message I've never seen before when I installed my
> application on a client's machine.
> I've got seven machines at this location that all work fine, when I
install
> on a new machine, I can connect through ODBC Administrator; but, when I
try
> to connect through the program I get this error message:
> [ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
> [ODBC SQL Server Driver][TCP/IP
> Sockets]ConnectionOpen(SECDoClientHandsh
ake()).
> I've looked on KB and have not been able to find anything specific on
this
> problem.
> Any ideas?
> Thanks in advance.
>

ODBC driver needed for Compact Edition

I have the newest 'Everywhere' Compact Edition installed, and have created a new desktop database using VS 2005 after installing the VS 2005 SP1 Beta, all successfully. I have no need to use the Mobile components and no need to syncronize to a mobile device. I can connect to the database programatically in VB.NET no problem.

Instead, I want to connect to the desktop database using MS Access. So far, I can't connect using the standard (old) SQLServer ODBC driver, and haven't found any new driver, either. Am I just premature and need to be patient? Does anyone know if there's one in the works? Or am I the only one to have thought of it?

Any help would be appreciated.

Thanks

Merle Nicholson

SQL Server Compact (was Everywhere) Edition does not have ODBC Driver. It has OLEDB and ADO.NET providers right now.

Thanks,

Laxmi

ODBC driver for windows 2003 64bit

Hi All,

I have installed windows 2003 R2 64bit on one of the system, but my devlopment team pointed out that there is no odbc driver available.

I check it for odbc driver on OS cd but i do not found any relevant files/packages, can any one tell me from where I can download the ODBC driver for windows 2003 64bit OS.

Thanks & Regards

Varian

An ODBC driver connects to a particular database backend server (Oracle, SQL Server, etc). What specific ODBC driver are you looking for?|||

There is definitely a SQL Server driver for 64-bit. SQLSRV32.DLL ships with the OS, and SQLNCLI.DLL (used with SQL Server 2005) can be downloaded from the microsoft website.

I think you may be correct, though, about non-SQL Server drivers no being available on 64-bit clients.

|||

I have the same problem. My company works with the windows server 2003 R2 64 bits and we can't use an Access DB in our Site because this version doesn't have the drivers for accessing Access Databases. Can someone help?

Thanks

|||

Hi,

Can you help me with ODBC drivers for MS Excel and MS Access... My organisation needs the same.

Regards

Ramakrishnan M

|||

Try looking at the post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1, which I believe answers your question. Here's a clip:

64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.

Pak-Ming Cheung,

MDAC Team, MSFT.


ODBC driver for windows 2003 64bit

Hi All,

I have installed windows 2003 R2 64bit on one of the system, but my devlopment team pointed out that there is no odbc driver available.

I check it for odbc driver on OS cd but i do not found any relevant files/packages, can any one tell me from where I can download the ODBC driver for windows 2003 64bit OS.

Thanks & Regards

Varian

An ODBC driver connects to a particular database backend server (Oracle, SQL Server, etc). What specific ODBC driver are you looking for?|||

There is definitely a SQL Server driver for 64-bit. SQLSRV32.DLL ships with the OS, and SQLNCLI.DLL (used with SQL Server 2005) can be downloaded from the microsoft website.

I think you may be correct, though, about non-SQL Server drivers no being available on 64-bit clients.

|||

I have the same problem. My company works with the windows server 2003 R2 64 bits and we can't use an Access DB in our Site because this version doesn't have the drivers for accessing Access Databases. Can someone help?

Thanks

|||

Hi,

Can you help me with ODBC drivers for MS Excel and MS Access... My organisation needs the same.

Regards

Ramakrishnan M

|||

Try looking at the post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1, which I believe answers your question. Here's a clip:

64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.

Pak-Ming Cheung,

MDAC Team, MSFT.


sql

Wednesday, March 28, 2012

ODBC driver for windows 2003 64bit

Hi All,

I have installed windows 2003 R2 64bit on one of the system, but my devlopment team pointed out that there is no odbc driver available.

I check it for odbc driver on OS cd but i do not found any relevant files/packages, can any one tell me from where I can download the ODBC driver for windows 2003 64bit OS.

Thanks & Regards

Varian

An ODBC driver connects to a particular database backend server (Oracle, SQL Server, etc). What specific ODBC driver are you looking for?|||

There is definitely a SQL Server driver for 64-bit. SQLSRV32.DLL ships with the OS, and SQLNCLI.DLL (used with SQL Server 2005) can be downloaded from the microsoft website.

I think you may be correct, though, about non-SQL Server drivers no being available on 64-bit clients.

|||

I have the same problem. My company works with the windows server 2003 R2 64 bits and we can't use an Access DB in our Site because this version doesn't have the drivers for accessing Access Databases. Can someone help?

Thanks

|||

Hi,

Can you help me with ODBC drivers for MS Excel and MS Access... My organisation needs the same.

Regards

Ramakrishnan M

|||

Try looking at the post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1, which I believe answers your question. Here's a clip:

64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.

Pak-Ming Cheung,

MDAC Team, MSFT.


ODBC Driver for SQLServer Everywhere/Compact from Access

So far I've been unable to connect to a test SQLServer Everywhere/Compact database with MS Access. I installed the new SQLServer 2005 Native Client to no avail. Has anyone done this?

If you are trying to sync the data between Access and the SQLServer Compact edition, you might need to download the synchronizer. The following link should provide you a quick overview and the access to the software. If this is not what you intended to do, please provide more details on what you are trying to accomplish:

http://www.microsoft.com/downloads/details.aspx?FamilyID=B967347A-5DD0-445C-8A9F-AEA3DB9EC4BC&displaylang=en

Regards,

Riyaz

|||

In Access, I'm simply trying to link to a SQLServer CE database using an ODBC driver, as you can do with other SQLServer servers. I've been the route you suggested, hoping that in the process I'd discover the driver I need. But to install that synchronizer, I have to install IIS and SQLServer 2005, which goes beyond what I'm trying to do. And I'm not interested in syncronizing to a mobile device in any case.

I was hoping to use SQLServer CE as a substitute for the normal Access Jet engine, to take advantage of encryption and security that Access does not provide (or does poorly). I want to deploy a single-user Access application with an easily deployable secure database. I'm doing it now with just Access, but I'd like to make the data tables inaccessible except through my application.

Thanks for the suggestion.

|||You can only connect to an instance of a SQL Server 2005 Mobile Edition database when it is running on a Windows CE-based OS or Tablet PC (you can create a SQL Server 2005 Mobile database in Visual Studio and, I believe, SQL Server Management Studio as part of the development process). When SQL Server Everywhere becomes available, it should, as you've surmised, fit your needs. In the meantime, you can check out the development experience using SQL Mobile today...take a look at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/sqleverywhere.asp?frame=true for some additional info. If you'd like to have a runtime prototype of your app, however, you'll want to try using SQL Server 2005 Express.|||

I do have SQL Server 2005 Everywhere installed, (SQL Server 2005 Compact Edition), and I've created a database from VS 2005 (after installing VS 2005 SP1 Beta) and so far have not been able to connect to that database from Access. There is a .dll distributed with Everywhere: sqlceoledb30.dll that has a description "OLEDB Provider" that I am hoping will work, but it is not installed as an ODBC driver.

It seems impossible that I'm the first to attempt this. Any help will be appreciated.

Office 2003 SP2, Win XP SP2, VS 2005 SP1 Beta

Thanks

|||

The naming is a little tricky here...SQL Server 2005 Mobile Edition is the 3.0 version of the product formerly referred to as SQL Server Compact Edition (or SQL CE). The product formerly referred to as SQL Server Everywhere now appears to have the moniker of SQL Server 2005 Compact Edition...this version is the only one in this family that can be used on the desktop. A CTP version of this product was released in late August and the RC1 version is now available at http://www.microsoft.com/downloads/details.aspx?FamilyId=85E0C3CE-3FA1-453A-8CE9-AF6CA20946C3&displaylang=en

Given all of this, which version do you have? The RC1 file version appears to be 3.1 (the device only SQL Server 2005 Mobile Edition would be v3.0, I believe).

If you have the correct version but continue to have problems connecting, I'll move this thread into the SQL Server Compact Edition forum.

|||

If you read the last post I made, it's pretty clear that I have Compact Edition 3.1 RC1 Beta. I haven't ever installed the Mobile Edition. After installing CE, most references (like the installation directory) reflect the previous name (Everywhere).

I really want to link to a Compact Edition database through ODBC (as it happens, in Access). I can connect to it fine in VS 2005 VB.NET, so I don't think it's a lack of understanding.

Thanks, any help will be appreciated.

|||Thanks for claryifying the specific version that you have installed. Someone here in the SQL Server Compact Edition forum should be able to help you with the nuances of connecting to a local SQL Server CE database.|||

Although SQL CE 3.1 does expose an OLE DB provider, you cannot link to it via the regular ODBC link in Access. I have developed a set of tools that will help you with both converting to and from Access and also to edit the SDF on the desktop. These tools use the OLE DB provider at the low level and work with databases on the PC and on the device. You can try them here: http://www.primeworks-mobile.com

Friday, March 23, 2012

ODBC Connection to SQL Server 2005sp2 Installed on VISTA.

Hi people i am getting a problem when im creating a dsn to sonnect the SQL server as the database for my content server.....................i tried all the tricks given by you people but its still not workin it is showins a message that .............

Connection failed.

SQL State'01000'

[Microsoft][ ODBC SQL Server Driver][Named Pipes]Connection Open

(Connect()).

Connection Failed:

SQL State:'08001'

SQL Server Error:17

[Microsoft ][ODBC SQL Server Driver ][Named Pipes]SQL Server doe not exists or access denied............................

Please any body can help me out with this problem..............?


--
Chetan

Hi Chetan,

This seems like a typical connectivity problem probably not related to Vista. Please follow the instructions for posting a connectivity question from the following links:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=975683&SiteID=1

HTH,

Jivko Dobrev - MSFT

--

This posting is provided "AS IS" with no warranties, and confers no rights.

sql

ODBC connection to remote SQL srver failed

Hi all,
Here is the scenario.
I installed SQL server 2000 on a NT server which already has SQL
server 6.5. This is because I want to upgrade the 6.5 to 2K. The 6.5
is the default instance, and the 2K is in a named instance.
Everything went well up to this point. I can bring up both instances
and transfer database over.
Now, the 6.5 server has been brought down due to not in use. I have a
Access mdb file with linked tables to the SQL 2K server by using a
created file DSN in ODBC manager. Everything works fine. I can open
tables and see data. But if I try to open the same Access mdb file
from remote machines, Win 95s & Win 98s, (using shortcuts points to it
on the NT machine), I get error "ODBC connection to SQL server
<my2Kserver>\<my2Kinstance> failed".
So, opening it from same machine works, opening it from remote does
not. Any ideas? By the way, I tested the network connection and it
works. Becuase I can see the shared drive and files of NT server from
other remote machines.
HansHello Hans,
H> So, opening it from same machine works, opening it from remote does
H> not. Any ideas? By the way, I tested the network connection and it
H> works. Becuase I can see the shared drive and files of NT server
H> from other remote machines.
I think, your 95's or 98's account have not enough access rights for file
operations with MDB files on the server.
Igor Shekalev, http://www.sqledit.com, SQL editor with ODBC support|||As noted above, since you are using an ODBC file DSN, check to make sure you
r client systems have read permissions on the file DSN folder.
Another thing you might try doing is updating to the latest version of MDAC
on all of your client systems that will be using the SQL Server. I know tha
t I've had serious connectivity issues with Win95 and Win98 systems to my SQ
L 2K server before installing the latest updates, particularly after the app
earance of the SQL Slammer virus last year, since MSSQL SP3 significantly ch
anged the connection protocol that SQL Server uses.
You can find the installation information for MDAC 2.7 here:
http://support.microsoft.com/defaul...10&Product=mdac
Note that MDAC 2.7 is the version that is installed with SQL Server 2000 SP3
.
If you want the latest and greatest, MDAC 2.8 is also available.
http://www.microsoft.com/downloads/...&displaylang=en
Hope this helps.
Jimsql

ODBC Connection SQL Server Error

Hello, my VB app fails to connects to a SQL Server.
Server side info
SQL Server is installed in a W2000 PC configured for IIS use. It is not a PDC.
Client side info
W2000, no Access app installed.
Situation:
System DSN created with ODBC config utility works fine and connects succesfully to the server. But when a connection is tried to be made through app it fail: "Login failed, ... user(null)... Not associated with a trusted SQL Server connection"
Any suggestions ?
Thanks
Arnaldo
Arnaldo,
See if this helps
'PRB: ASP/ODBC/SQL Server Error 0x80040E4D "Login Failed for User '(Null)'"'
http://support.microsoft.com/?id=307002
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Arnaldo" <anonymous@.discussions.microsoft.com> wrote in message
news:ADBEE679-C4F6-486C-96CB-1588892D7283@.microsoft.com...
> Hello, my VB app fails to connects to a SQL Server.
> Server side info
> SQL Server is installed in a W2000 PC configured for IIS use. It is not a
PDC.
> Client side info
> W2000, no Access app installed.
> Situation:
> System DSN created with ODBC config utility works fine and connects
succesfully to the server. But when a connection is tried to be made through
app it fail: "Login failed, ... user(null)... Not associated with a trusted
SQL Server connection"
> Any suggestions ?
> Thanks
> Arnaldo
>
>
>

ODBC Connection SQL Server Error

Hello, my VB app fails to connects to a SQL Server.
Server side info
SQL Server is installed in a W2000 PC configured for IIS use. It is not a PD
C.
Client side info
W2000, no Access app installed.
Situation:
System DSN created with ODBC config utility works fine and connects succesfu
lly to the server. But when a connection is tried to be made through app it
fail: "Login failed, ... user(null)... Not associated with a trusted SQL Ser
ver connection"
Any suggestions ?
Thanks
ArnaldoArnaldo,
See if this helps
'PRB: ASP/ODBC/SQL Server Error 0x80040E4D "Login Failed for User '(Null)'"'
http://support.microsoft.com/?id=307002
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Arnaldo" <anonymous@.discussions.microsoft.com> wrote in message
news:ADBEE679-C4F6-486C-96CB-1588892D7283@.microsoft.com...
> Hello, my VB app fails to connects to a SQL Server.
> Server side info
> SQL Server is installed in a W2000 PC configured for IIS use. It is not a
PDC.
> Client side info
> W2000, no Access app installed.
> Situation:
> System DSN created with ODBC config utility works fine and connects
succesfully to the server. But when a connection is tried to be made through
app it fail: "Login failed, ... user(null)... Not associated with a trusted
SQL Server connection"
> Any suggestions ?
> Thanks
> Arnaldo
>
>
>

ODBC Connection Setup

I'm running SBS 2003 Premium SP1 and all is well. I've installed a new SQL
based application that requires a simple ODBC connection to the SQL database
.
I have about 50 PCs to setup this ODBC link to my SBS server and there must
be a faster way to do this via a script or through Group Policies.
Has anyone tried this and how? I've used GPs for simple things like folder
redirection, but I'm not that strong on it.
Thanks.
KenI've taken to using file-based DSNs placed in a server folder that everyone
can access. It's turned out to be the best solution in my case.
Randall Arnold
"shepcon" <shepcon@.discussions.microsoft.com> wrote in message
news:E02D79DC-D435-4C36-9FF8-4C541F6116D4@.microsoft.com...
> I'm running SBS 2003 Premium SP1 and all is well. I've installed a new
> SQL
> based application that requires a simple ODBC connection to the SQL
> database.
> I have about 50 PCs to setup this ODBC link to my SBS server and there
> must
> be a faster way to do this via a script or through Group Policies.
> Has anyone tried this and how? I've used GPs for simple things like
> folder
> redirection, but I'm not that strong on it.
> Thanks.
> Ken
>sql

ODBC Connection Setup

I'm running SBS 2003 Premium SP1 and all is well. I've installed a new SQL
based application that requires a simple ODBC connection to the SQL database.
I have about 50 PCs to setup this ODBC link to my SBS server and there must
be a faster way to do this via a script or through Group Policies.
Has anyone tried this and how? I've used GPs for simple things like folder
redirection, but I'm not that strong on it.
Thanks.
Ken
I've taken to using file-based DSNs placed in a server folder that everyone
can access. It's turned out to be the best solution in my case.
Randall Arnold
"shepcon" <shepcon@.discussions.microsoft.com> wrote in message
news:E02D79DC-D435-4C36-9FF8-4C541F6116D4@.microsoft.com...
> I'm running SBS 2003 Premium SP1 and all is well. I've installed a new
> SQL
> based application that requires a simple ODBC connection to the SQL
> database.
> I have about 50 PCs to setup this ODBC link to my SBS server and there
> must
> be a faster way to do this via a script or through Group Policies.
> Has anyone tried this and how? I've used GPs for simple things like
> folder
> redirection, but I'm not that strong on it.
> Thanks.
> Ken
>

Wednesday, March 21, 2012

ODBC connection for client application to SQL Server 2005 Express installed on network computer

Hi All,

I've developed an application that connects to a SQL Server 2005 Express database. I created a DSN to connect to the database through ODBC. Currently, I am testing locally and everything works fine.

I would now like to install my application on another workstation and connect remotely to the database located on my development machine.

The client workstation does not have SQL Server 2005 Express installed on it because I would just like my application to connect remotely by creating the DSN and using ODBC. What I'm missing here are the database drivers. The "SQL Natice Client" is not available on this client workstation. How can I deploy the necessary drivers with my installation file so that I may create the required DSN name using the SQL Native Client driver?

Thanks!
Deployment of the SNAC can be found here:

http://msdn2.microsoft.com/en-us/library/ms131334.aspx

If you don′t use the new features of SQL Server 2005, you can also use the MDAC driver which is compatible with the Pre SQL 2005 features of SQL Server 2005.

My best practice is not to use the DSN rather than using direct connection strings which can be configured in configuration files.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de
|||Thanks for the reply.

I can't seem to find the sqlncli.msi file on my drive. I have the Express edition installed. Is there somewhere else I can find this installer for the SNAC driver?

If not, which version of MDAC do I need, and how would I build my DSN? I agree with using connection strings instead of DSN's, unfortunately that is a decision I'm unable to change.

|||

SNAC: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc
it

Just get the newest MDAC, since it makes no difference if you get 2.7 or 2.8 but getting the newest will keep you away from old bugs :-)

The connectionstrings can be found on www.connectionstring.com (Where I also posted an example for the SNAC one :-) )

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Excellent,

I got it working using MDAC.

Thanks!

ODBC Connection Failure

I am having a problem getting the ODBC driver to connect.

I just installed VS2005 and can't connect to my SQL2000 server. It is there. I can't connect using either one of the mix mode authentication.

I can login to SQL from another pc when logged in with this user name. It has to be something on this pc blocking it.

Iam not rying to do this from a ASP web page just trying to setup a ODBC driver and I get these errors.

I get the error:" Login failed for user (null)" Not associated with a trusted connection

Thanks

Mike

I downloaded and installed manager studio and I can see the server in the network tab but still can't connect. I get the error 11001

Any Ideas?

Thanks

|||

Let's see your connection string. I would also read: http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html

|||

This link was broken for a while and I could not reply.

William,

Little background. I have had this application up and running since Oct 05 with the connection string on several different pc's.

There is no problem with the connection string.

I recently had difficulty on two new PC, one laptop and one desktop. Neither could access SQL2000 running on another PC. Both could run the application and connection string locally if I copied the DB down to express. This application is a smart client app not an ASP app.

Both instances had newly installed VS2005 and SQL Express installed on them.

I could not even set up a DSN using ODBC manager. It would not connect to the SQL 2000 server.

When I tried using SQL Mgr Studio Express, it could see the SQL 2000 server but not connect to it.

I always got some kind of connection error.

Thanks.

Monday, March 19, 2012

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

ODBC Call fail - Strange behaviour

Hi.
I just installed Sql server (in fact MSDE) and exported my Access 2002
projet to this database instance.
I then linked my Sql server tables within my access project.
I get a strange behaviour for some queries. I receive the message 'ODBC -
Call fail'. It seems to be a timeout pb.
The query involves two tables.
I checked my query. Everithing is ok.
I checked the first table. I can read data and filter it.
I checked the second table. I can read data, but if I want to filter any
column, I get an ODBC call fail. The table contains only 802 records.
Any idea ?
Configuration :
MSDE Rel A on XP home SP1.
Access 2002 client, MDAC 2.8, on XP Pro.
Check your data on the SQL server. You may have some data that is null and
the SQL server table def is not allowing nulls? Just a thought. Usually
these errors are caught during the import process...
I would start by creating a brand new query and only add one column at a
time. See if you can then sort on that column. Carry on like this - adding
new columns each time until the error happens. Then check that columns data
on the SQL server so see if there happens to be null values present...
"Alain" <alain.roghi_nospam@.laposte.net> wrote in message
news:uU5H9BEmEHA.2180@.TK2MSFTNGP12.phx.gbl...
> Hi.
> I just installed Sql server (in fact MSDE) and exported my Access 2002
> projet to this database instance.
> I then linked my Sql server tables within my access project.
> I get a strange behaviour for some queries. I receive the message 'ODBC -
> Call fail'. It seems to be a timeout pb.
> The query involves two tables.
> I checked my query. Everithing is ok.
> I checked the first table. I can read data and filter it.
> I checked the second table. I can read data, but if I want to filter any
> column, I get an ODBC call fail. The table contains only 802 records.
> Any idea ?
> Configuration :
> MSDE Rel A on XP home SP1.
> Access 2002 client, MDAC 2.8, on XP Pro.
>

ODBC and SQLServer : does I need the client installed on ?

Hi,

Does I need to install the mssql client binaries to use ODBC to
connect to a mssql database ?

TYIA
rjp"rjp" <rjp.l@.laposte.net> wrote in message
news:9b7a7215.0402100934.5fe5b830@.posting.google.c om...
> Hi,
> Does I need to install the mssql client binaries to use ODBC to
> connect to a mssql database ?
> TYIA
> rjp

You should be able to use the latest version of MDAC - there's a link from
this page:

http://msdn.microsoft.com/data/

Simon|||rjp (rjp.l@.laposte.net) writes:
> Does I need to install the mssql client binaries to use ODBC to
> connect to a mssql database ?

ODBC comes with MDAC that comes with Windows, so you don't need to install
anything - if you are on a Windows box, that is. (And it's a decently
modern version of Windows. Windows 95 is not likely to have any MDAC.)

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Friday, March 9, 2012

ocx error

when im trying to open some project im getting the error-
CRYSTL32.OXC could not be loaded
i already installed the ocx, so whats the problem?
what to do?
thanks in advancedanyone?|||anyone?:wave: :wave:
Do a search on your system for "CRYSTL32.OCA" and delete all the files you get.
Register the crystl32.ocx again and then try re-opening your project.:thumb:

hope this helps..

PS: In the mean time you could also check the knowledge base for Crytal reports here
support.businessobjects.com|||there is no "CRYSTL32.OCA" on my computer
and i checked the link...
what else can it be?
thanks|||"CRYSTL32.OCX" is for Crystal Reports, right? It's not something you created?

I had a similar problem with controls *I* created a while ago. Was using two seperate projects, one for custom user control and one for program. Would get same err whenever I made changes to usercontrol and recompiled.

Solution was to use vbg and group my controls and program together, to keep 'em in synch.

This is *probably* not your situation, but perhaps someone with a problem like I had will come across this. :)|||yes, its not something i created..so thats not the problem|||Did you used REGSVR32.EXE, I don't know if you need to use it for Crystal Report, but usually, you need to register OCX you want to use in VB.

JeffB|||where is REGSVR32.EXE ? im a little bit new in this...

i just instaled the vb6 and crystl32.inf
what else i need to do?
thanks.|||This is some infos on REGSRV32:

http://support.microsoft.com/kb/q267279/

I'm moving this to CR forum ;)

JeffB|||its working now
thanks for the help|||I have some problems with Crystal Report program.

In my project I use VB 6.0 with SP6 and Crystal Report 10.0
The operating system is: Windows XP SP2

When I open the project, the system gives me this error message:
(Error during load: the Crystl32.ocx file could not be loaded)

Also I can not export my project as .exe because of the above problem.


I tried to replace the file of Crystl32.ocx with new versions but the problem is still being.

Also I tried to register the Crystl32.ocx file by using this command:
(Regxvr32 D:\Windows\System\crystl32.ocx /u) but this command does not work and the problem is still being.

please help me.

Thanks;|||>>Regxvr32 D:\Windows\System\crystl32.ocx /u) but this command does not work and the problem is still being.

What is the error you are getting?
If possible reinstall CR
or check out here
http://support.businessobjects.com/

Wednesday, March 7, 2012

Obtaining the version of ADO installed on XP

How is it possible to tell which version of ADO is installed on an XP workstation?

ThanksOne method is with the ADO Connection object Version property. VBScript
example:

Set connection = CreateObject("ADODB.Connection")
MsgBox connection.Version

--
Hope this helps.

Dan Guzman
SQL Server MVP

"Alan Taylor" <alan.taylor8@.abbey.com> wrote in message
news:e821d807.0412160429.79b36010@.posting.google.c om...
> How is it possible to tell which version of ADO is installed on an XP
> workstation?
> Thanks