[YBeauchamps]

Hi Folks,

I have some btrieve files including their ddf files that I want to export into SQL. The issue is i'm having some problem reading the files themselves. I have downloaded some tools such as BTSearch or even tried to connect to them using Pervasive ODBC driver. However I keep getting the same error (Status Code - 11). I've been looking this up and it appears that it is quite possible that there is a hard coded UNC path in the ddf files.

If that is the case the only utility I could find that might fix this is something called "UpdtTabl" from Goldstar Software. The tool is only $100 which isn't too bad but I'm still not 100% sure that this is in fact my issue I'd rather not take the chance.

So basically I need any input as to whether or not anybody has any experience with any utilities or viewers that would allow my to check the ddf files to even see if the UNC is in fact hard coded.

Note: I have copied the said files over to windows but I still have access to the originals on the Novell server. I'm just not familiar with Novell but if it's easier to do it on that side I'm open to suggestions.

Thanks,

[mirtheil]

If you can access the DDFs/files from PCC, you can issue a "SELECT * FROM X$FILE" query. This will list all of the tables and the physical path.
There is another tool available for fixing the DDFs if they have hardcoded paths. You can use my DDF Path Fixer (http://www.mirtheil.com/pathfixer.asp).

[nelsonsoft]

The problem could be the path you have the files in. Change the path to use hte 8.3 naming convention with no spaces in the directory names.

BtSearch also should allow you to view the file path in the DDF files. But more than likely your path was not using the older 8.3 format. What version of Pervasive Btrieve are you using on your Windows computer? Also you do not want to access your live files with an older and newer version of the drivers. You should work with them off line.

Gil