The free DDF Builder, included with PSQLv10 does a decent job, but its not as intuitive to use from a user-interface standpoint. The "easiest" solution for the do-it-yourself-er is BTSearch. Also, the fields that are NOT defined as keys can have a wide variety of data types, so many times we are just guessing as to what may be in the fields. Someone who knows the application would need to provide field names. Note how I could get some fields very easily from the structure, but I have no field names - they are just bytes to the database. If you are making your own DDF's, then you must understand the data structures of the application. You don't have the metadata, so you must go through the process of making the DDF's (or contact the original developer to obtain DDF's if they have them). The data dictionary files, indicated in the paper and by Mirtheil, contain the metadata that make this "easy", and you can export directly from there. MsgBox "UploadPipe.You are seeing it as easy as it gets. ' The delimiter can be set either before or after the cell value Open " \\filepath\UploadPipe.dat" For Output As #1įor Each myRecord In Worksheets("Dat Test").Range("B4:B" & Range("B" & Rows.Count).End(xlUp).Row)įor Each myField In Worksheets("Dat Test").Range(.Cells, Cells(.Row, Columns.Count).End(xlToLeft)) ' this is the path to where you want the output file to go ' The delimiter can be set to any value depending on requirements Kindly help me write my destination folder. However, when I used his code, I run into errors on the path to where the output will go. It solved his problem on the code given by one of the members here. Actually, I have found a similar case here but it posted way back 2014.
0 kommentar(er)
