dat & idx files

[Fornatian]

A friend has asked if I can extract some information from a non-copyright public datasource CD for use in a mailshot.

I have loaded the program, it unzips with files with .dat and accompanying .idx extensions. I understand that characteristics of each of these types of file.

I am not sure if the program that created the CD was a Borland database, but I suspect so. I can't categorically say that the CD is a self-supporting exe because my machine has been subjected to so much loading/unloading I don't know what's on it and what isn't that might permit the data to be viewed.

I can open the file as text but without the interpretation of the idx file the info is garbage.

This is going to be a simple one for someone, but I just can't fathom it, but I think that's because I don't have the source program on my machine.

I have tried importing the data as delimited and fixed width on numerous occasions using every driver(Foxpro,Paradox, you name it..). No luck

Thanks in advance for any thought, inspiraton or direction.

 

[Fornatian]

Further information suggests this may be a Foxpro table, does anyone have any experience with such things? Do I need to have Foxpro installed to read the tables? I have a Foxpro driver on my PC but it isn't recognising the file.

 

[WayneRyan]

Fornation,

I think that FoxPro stores the info in the same way as DBase,
as a .DBF file.

Just a chance, make a copy with a .DBF extension and try
to import it as a DBase file.

Wayne

 

[Fornatian]

Thanks wayne, unfortunately I've tried that already, no avail.
I am writing a script to extract the info but FoxPro inserts 'dirt' into the file to encrypt it - sporadic returns and non-printing characters apparently at random intervals. By changing all non-alphanumeric characters and sentence characters I have had limited success, however it is not working successfully because of the 'dirt' which I can't eradicate. The method I am following is to eradicate all hard and soft return characters then ID what consitutes an end of record character/character set, then use a find and replace in Word to replace this with a return mark.
That is unless anyone has FoxPro 2 and could do me a favour:creep, beg:

 

[WayneRyan]

Fornation,

If you can find some with FoxPro2, and get them to export the
data in a more usable manner, then that's the way to go.

How much data is there? Can you post a zipped copy here?

Wayne

 

[Fornatian]

Sorry for not getting back sooner, I've been taken off my normal job of enforcing licensing laws to assisting in conversion of our poor database information to an equally inadequate unix system database. When will people learn that a customised built package with good support is better than a homogenous cheaper per entry package with a million compromises.

Anyway, rant over, I've check the file sizes of the dat and idx files, and they are 3 meg plus, so unfortunately I can't post for the angelic individual.

I may have sorted it anyway by getting a long standing IT bod to have a look at the filesfor me. I mean, not as I couldn't sort it out myself but you can only do so many things in a day(,moan!!).

Cheers for your assistance anyways, it nice to get a return on investment

Ian

 

[dcx693]

The tables might be FoxPro. I did a project recently with FoxPro data. I saw the dbf files and thought they might be really easy to import, but NO. I had to download updated Data Access components from Microsoft to get the latest FoxPro ODBC drivers in order to import the files from here: http://msdn.microsoft.com/vfoxpro/downloads/addons/odbc.asp

If they are FoxPro files, you can't import the dbf files directly. You need to set up the files as an ODBC data source (using the ODBC applet in the Control Panel) go to File, Get External Data, Import (or Link), and choose ODBC, then point towards the ODBC data source you created previously. Very annoying learning process for me, hopefully it can help you.