Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
SQL ODBC driver compatibility
Message
De
02/09/2015 12:03:39
 
 
À
02/09/2015 10:22:50
Information générale
Forum:
Visual FoxPro
Catégorie:
Client/serveur
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows Server 2012
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Desktop
Divers
Thread ID:
01623958
Message ID:
01624177
Vues:
60
>>>We use 11 in production for perhaps 120 users. We use memo fields extensively, and there are no reported issues.
>>
>>How can I check which version I have installed on my machine? When does this get installed?
>>
>>I don't specifically remember installing an ODBC package, so it must have come in from when I installed FoxPro, or Sql Server Express, I would guess.
>
>Find the 32-bit odbc administrator -- easy in Win 8.1, where the 32-bit and 64-bit are listed when you search on odbc. Otherwise, go to syswow64 (on x64 machines) and start odbcad32.exe.
>
>Look in the list of drivers.
>
>We have had problems using the default driver often installed on servers (SQL Server -- dates back to SQL 2000). We have had no problems (because we map field types in the remote views) using the newer drivers.
>
>hth,
>
>Hank

Okay, thanks for this guidance... Here's what I've learned about my setup. (Also, see attached screenshot if needed.)

On my Windows 8.1 Professional, 64-bit developer machine, I have VFP 9 fully patched up, and I am running Sql Server Express 2012. I am developing my VFP/Sql Server app on this development machine, but will be running against Sql Server Express 2014 on a Windows Server 2008 R2 Standard 64-bit box very soon, so it might be smart for me to learn a little bit more about this before we go live.

I have the following drivers installed on my local dev machine:

It shows 2 "Sql Server" entries on the "Drivers" tab.

"Sql Server" version 6.03.9600.17415 file: SQLSRVR32.DLL date:10/28/2014

"Sql Server Native Client 11.0" version 2011.110.3000.00 file: SQLNCL11.DLL date: 10/20/2012


So, next I looked to see what connection string I am using in my VFP app to connect to the Sql Server.
    lcConnectionString = "driver={sql server}; server=MSPC5\SQLEXPRESS; database=lmdb7; uid=XXXXX; pwd=XXXXX"
So, it appears that I'm using version 6.03 driver, right?

Then I changed my connection string to use "Sql Server Native Client 11.0", and the app appears to run without issue so far.
    lcConnectionString = "driver={Sql Server Native Client 11.0}; server=MSPC5\SQLEXPRESS; database=lmdb7; uid=XXXXX; pwd=XXXXX"
So, I still am very curious to understand from whence each of these 2 drivers were installed on my machine. I do not specifically recall installing either one of them, so I assume they got installed either with the OS or when I installed some other software, like perhaps Sql Server Express 2012.

Regardless, I'd love to know some specific details of what advantages (or problems) I might have based on which one I am using. Heck, from ver 6 to ver 11 sounds like a lot just based on the numbers, but surely there must be some info "out there" somewhere to guide me on which one I should be using.

I assume that each client machine will need to have the specified odbc driver installed on their machine, right? So, I better run around to all of the 7 machines in our office that will be running this app, and see what they each have in common.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform