Hello I have a problem. I need to export data from Cobol data files (dat, inx) to anything else (txt, cvs, excel access, whatever).

Chapter 15: Converting DG COBOL Data Files. This chapter describes the Convert5 utility, which you must use to be able to convert your DG Interactive COBOL data files to Micro Focus COBOL data file format. When you use the Convert5 utility, a file conversion program is produced, which itself can be used to convert your.

I need to do this using C# and.NET platform. But I cannot open or read this files (I tried as flat file with fixed row size and separator, I tried different data readers like SiberDataViewer or even simple notepad) if open file I can see only strange characters. I wonder I anyone know some ODBC driver or data reader which will be able to open and read this files (free or with demos, trials to check if it works witch my dat,inx files before I buy it). About files – I know that they contain information about daily incomes/outcomes, guests, rooms, services etc. Third Reich Patch 1.38. In hotel chain. Hotels use Cobol application called ReHot which store data in dat(data), inx(indexes) files. Software vendor of course won't help and application cannot export data to different files only print them on fiscal printer. Gps Utility 5.15 Crack.

I will be very glad for any help/advice/suggestion you can offer me to solve this problem. Piter RE: export data from Cobol data files (Programmer) 22 Oct 08 06:30. It sounds like some kind of VSAM implementation (DAT = records themselves; IDX = index to the records). The first thing that would be useful would be to identify the compiler/development environment that this program was created in, which might shed some light on the files involved. The files are in simple binary code, unless some encryption hasn't been applied.

Which means it would be useful if you had the source describing the record format of these files. Download The Beatles Wii Game. If I read your post right in saying that 'the vendor won't help', that probably means all you have is the executable, which means you won't have this. The vendor would have likely made this closed-source, which probably means there are EULA considerations involved. Speaking of which, I'm not finding anything when I google the terms you used. Anyhow, unless you have the record format of the file (Is this on the vendor website?), you're pretty much out of luck.