"Specified cast is not valid" with ODBC about sqlprovider HOT 10 CLOSED

@simonhdickson one for you sir?

@snorehorse, you may need to give some more details such as the exact DSN details and perhaps a schema for us to replicate.

out of interest though, as you are using sql server, why not just use the sql server provider and a normal connection string instead of ODBC? The ODBC support is necessarily a lot less thorough - although this should still work and give you basic access to the database. I'm guessing you have a need to use the DSN.

from sqlprovider.

I pasted the sql I used to create the database at: http://pastebin.com/5W3PPVaD
which is from Query Expressions (F#) http://msdn.microsoft.com/en-us/library/vstudio/hh225374(v=vs.120).aspx

from sqlprovider.

Cool, thanks, we'll look into it. Just so you know, the link to Query Expressions there uses the original Microsoft SQL provider, we don't support everything that is listed in those examples yet.

from sqlprovider.

If i change foo to foo1, which doesn't exist, I get "Data source name not found and no default driver specified" which shows that something is partially working behind the scenes :)

from sqlprovider.

great, I assume the DSN is just a normal SQL Server connection string, using integrated security or a standard sql login / password ?

from sqlprovider.

It's probably something silly, we should be able to address fairly easily (I hope!)

from sqlprovider.

@pezipink No prob "we don't support everything", I'm just interested in the most basic read features for my project. Thanks for what you've done so far anyway!

My situation is I'm building a desktop application and I'm thinking what would be the easiest for user configuration. It's my first application in F#. In previous projects I've used the ConnectionDialog source that was available from MS for a short time, to build a connection string. But I'm thinking, why try to build a connection string inside my program? Have the end user's IT guy use Data Sources (ODBC)... install whatever driver they choose... and then give them a dropdown list of the DSNs in my app. This way I don't have to worry about drivers if they change database providers in the future (as long as they aren't using something so esoteric that it breaks the functionality in the SQLProvider).

from sqlprovider.

Microsoft SQL Server Native Client Version 11.00.3000

Data Source Name: foo
Data Source Description: it whips the llamas foo
Server: SEAHORSE-PC\fooz
Use Integrated Security: Yes
Database: MyDatabase
Language: (Default)
Data Encryption: No
Trust Server Certificate: No
Multiple Active Result Sets(MARS): No
Mirror Server:
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Regional Settings: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes
Application Intent: READONLY

from sqlprovider.

@pezipink Yep I'll take a look at this one

from sqlprovider.

I've started working on a fix for this. This ticket finally gave me a reason to install MSSQL on my local machine. :)

from sqlprovider.