exporting ODBC driver to another computer using registry
Posted on 2013-06-06
I have a computer that has been configured to access a HYPERFILE SQL V14 a few years back (it was in 2009). I needed another computer with the same drivers, but our service provider gave us the V16 drivers, and the performance are really weak. It takes between 3 to 6 times longer to do the same things with the new drivers. Since I have batch jobs that takes a few hours to run, it would be very problematic to multiply by 3-6 the time needed.
I can't find any driver for this on their website, apparently it is to be deployed with applications developped in webdev.
I tried using the registry to get the configuration of the ODBC driver exported. I searched for "hyperfile SQL" in the registry and exported the values.
These are the values I exported :
and the following key and everything under it :
Then I went to the installation folder
c:\program files\common files\PC SOFT\14.0\ODBC
and copied all the files in there to the same location on the new computer.
It seems to work not too bad. I was able to create the ODBC datasource. I am able to browse the tables in the database.
But when I try to open most tables, I get an error : "ODBC error -- call failed". I don't have this error when I try to open smaller tables. The biggest table I could open had 24292 records.
I tried opening the table in visual basic, catching the error with "On error goto" but the only information I got this way is the number of the error., which is 3146.
I tried installing this driver on another computer the same way and got the same result. I suppose there is another configuration somewhere that will let me browse tables through the hyperfile driver when there are more then a certain number of records.
PS : The hyperfile ODBC datasource configuration has almost no options. I can define the name of the datasource, the path to the analysis file and the path to the data files. So this is not where I can configure a buffer size or something like that.
PPS : I'm using windows xp on all those computers. I also use access 2003 and VBA for programmation.