Somewhere years ago, I ran across a general description of a .FDF file, but I’ve long forgotten where it was.

It’s very rare that anyone needs to create a .FDF file with their own programming. Usually people just have iSeries Access create .FDF files automatically.

Why is it necessary to create one yourself? Maybe if we knew what general procedure you’re creating, we could suggest alternatives.

Tom

I’ve modified one by hand, but like Tom, years ago, before they changed their format from ‘simple and obvious – field, length, position’ to ‘not obvious – never had a need to look in there’

Anytime we need to automate a download, we create the transfer manually, if necessary by downloading the ‘target’ file to the PC to generate the transfer definition, then build it into the PC level app, where the file is created and transgerred.

Have you tried the manuals – and the fora?

Thanks for the reply, The ideas was that a user would create a sheet with data to be uploaded, the layout for the sheet needed to be flexibel Meaning flexible number of columns with aplha and/or numeric data. I wrote a macro which creates both the .FDF and the .DTT files. By pointing the user to the correct DTT file then he only needed to browse to that file and hit the OK button for the upload.
I created a workaround, so “if you can’t fix it you need to find something you can fix” Thanks again.