Jean,

On 6 Mar 2014, at 10:00, Jean-Baptiste Pressac 
<jean-baptiste.pres...@univ-brest.fr> wrote:

> Yes, you are right. The 7.1 ODBC Driver comes from the Client Connectivity 
> Kit (wavcz2zz.msi) installation whereas the 7.0 ODBC driver comes from the 
> installation of VOS pre-built binaries for Windows (C:\Program 
> Files\virtuoso-opensource\lib\virtodbc.dll).

[Hugh] I see what you mean I shall have the open source ODBC driver version 
updated to be 7.10.xxxx

> 
> By the way, if you install the Client Connectivity Kit, the registration of 
> the VOS ODBC driver as described in "Using Virtuoso Open-Source Edition on 
> Windows" should not be necessary ?

[Hugh] That is correct the installer used by the Client Connectivity Kit will 
automatically registered the ODBC Driver during installation.

> In that case, the procedure is not very clear, because I understood that I 
> should install the Client Connectivity Kit + run the DOS command to register 
> the virtodbc.dll in %VIRTUOSO_HOME%/lib. 

[Hugh] The  open source zip includes the ODBC Driver which you register 
manually as indicated in the docs for it and then you should not need to 
install the Client Connectivity Kit, as there is an ODBC Driver shipped with 
open source. 
> 
> 
> Anyway, it could be better to update the virtodbc.dll provided with VOS 
> pre-built binaries for Windows (provided on OpenLink Virtuoso Open-Source 
> Edition: Downloads) to the 7.1 version ?

[Hugh] Yes that will be done ..

Regards
Hugh

> Jean-Baptiste Pressac
> Traitement et analyse de bases de données
> Centre de Recherche Bretonne et Celtique
> UMS 3554
> 20 rue Duquesne
> CS 93837
> 29238 Brest cedex 3
> 
> tel : +33 (0)2 98 01 68 95
> fax : +33 (0)2 98 01 63 93
> Le 05/03/2014 18:39, Hugh Williams a écrit :
>> Hi Jean-Baptiste,
>> 
>> So the 7.1 ODBC Driver which is 64bit does work with your 64bit  Apache/PHP 
>> version, whereas the 7.0 ODBC driver which should also be 64bit is giving 
>> the windows 193 system error ?
>> 
>> Best Regards
>> Hugh Williams
>> Professional Services
>> OpenLink Software, Inc.      //              http://www.openlinksw.com/
>> Weblog   -- http://www.openlinksw.com/blogs/
>> LinkedIn -- http://www.linkedin.com/company/openlink-software/
>> Twitter  -- http://twitter.com/OpenLink
>> Google+  -- http://plus.google.com/100570109519069333827/
>> Facebook -- http://www.facebook.com/OpenLinkSoftware
>> Universal Data Access, Integration, and Management Technology Providers
>> 
>> On 5 Mar 2014, at 12:09, Jean-Baptiste Pressac 
>> <jean-baptiste.pres...@univ-brest.fr> wrote:
>> 
>>> I forgot the PHP script in my previous message : 
>>> <?php
>>> $conn   = odbc_connect('VOS', 'dba', 'dba');
>>> $query  = 'SELECT DISTINCT ?g WHERE {GRAPH ?g {?s ?p ?o.}}';
>>> $result = odbc_exec($conn, 'CALL DB.DBA.SPARQL_EVAL(\'' . $query . '\', 
>>> NULL, 0)');
>>> ?>
>>> <ul>
>>> <?php while (odbc_fetch_row($result)): ?>
>>>     <li><?php echo odbc_result($result, 1) ?></li>
>>> <?php endwhile; ?>
>>> </ul>
>>> 
>>> Finaly, I used a 64 bit version for my local Apache server and the script 
>>> works fine with the Openlink Virtuoso ODBC driver 7.10.3207.01 (C:\Program 
>>> Files\OpenLink Software\Virtuoso 7.0\bin) but there is a problem with the 
>>> Virtuoso Opensource ODBC driver 7.00.00.3203 (C:\Program 
>>> Files\virtuoso-opensource\lib), which generate a 193 system error.
>>> Jean-Baptiste Pressac
>>> Traitement et analyse de bases de données
>>> Centre de Recherche Bretonne et Celtique
>>> UMS 3554
>>> 20 rue Duquesne
>>> CS 93837
>>> 29238 Brest cedex 3
>>> 
>>> tel : +33 (0)2 98 01 68 95
>>> fax : +33 (0)2 98 01 63 93
>>> Le 05/03/2014 12:12, Jean-Baptiste Pressac a écrit :
>>>> Hello,
>>>> I installed Open-Source Virtuoso 07.10.3207 (64 bits, from Pre-built 
>>>> binaries for Windows) on Windows 7 SP1 (following Getting Started with the 
>>>> VOS Binary Distribution for Windows) and the last Client Connectivity Kit 
>>>> available (wavcz2zz.msi). Virtuoso was installed in folder C:\Program 
>>>> Files\virtuoso-opensource (in the 64 bits applications folder). I setup a 
>>>> DSN using the 64 bits version of odbcad32.exe (the one in system32) using 
>>>> Virtuoso Opensource ODBC driver 7.00.00.3203 (I also tried later the 
>>>> Openlink Virtuoso ODBC driver 7.10.3207.01). However, when I execute the 
>>>> following PHP script, I have the following error : "The specified DSN 
>>>> contains an architecture mismatch between the Driver and Application".
>>>> Did I something wrong ?
>>>> -- 
>>>> Jean-Baptiste Pressac
>>>> Traitement et analyse de bases de données
>>>> Centre de Recherche Bretonne et Celtique
>>>> UMS 3554
>>>> 20 rue Duquesne
>>>> CS 93837
>>>> 29238 Brest cedex 3
>>>> 
>>>> tel : +33 (0)2 98 01 68 95
>>>> fax : +33 (0)2 98 01 63 93
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> Subversion Kills Productivity. Get off Subversion & Make the Move to 
>>>> Perforce.
>>>> With Perforce, you get hassle-free workflows. Merge that actually works. 
>>>> Faster operations. Version large binaries.  Built-in WAN optimization and 
>>>> the
>>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Virtuoso-users mailing list
>>>> Virtuoso-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>> 
>>> <Jean-Baptiste_Pressac.vcf>------------------------------------------------------------------------------
>>> Subversion Kills Productivity. Get off Subversion & Make the Move to 
>>> Perforce.
>>> With Perforce, you get hassle-free workflows. Merge that actually works. 
>>> Faster operations. Version large binaries.  Built-in WAN optimization and 
>>> the
>>> freedom to use Git, Perforce or both. Make the move to Perforce.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk_______________________________________________
>>> Virtuoso-users mailing list
>>> Virtuoso-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Subversion Kills Productivity. Get off Subversion & Make the Move to 
>> Perforce.
>> With Perforce, you get hassle-free workflows. Merge that actually works. 
>> Faster operations. Version large binaries.  Built-in WAN optimization and the
>> freedom to use Git, Perforce or both. Make the move to Perforce.
>> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>> 
>> 
>> _______________________________________________
>> Virtuoso-users mailing list
>> Virtuoso-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
> 
> <Jean-Baptiste_Pressac.vcf>------------------------------------------------------------------------------
> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works. 
> Faster operations. Version large binaries.  Built-in WAN optimization and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk_______________________________________________
> Virtuoso-users mailing list
> Virtuoso-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Reply via email to