Re: variable size record length file parsing
- From: "Larry Serflaten" <serflaten@xxxxxxxxxxxxxx>
- Date: Mon, 14 May 2007 20:14:08 -0500
"Matt Williamson" <ih8spam@xxxxxxxxxxx> wrote
If anyone else wants to chime it, I'm listening.
You could use a class (just one instance) that exposes a Data property (String)
and all the other UDT members as properties. You would feed that class a
line at a time (via Data) and pull out the various properties for the output. That
would aloow you to do the whole file in one pass using Line Input.
Code in the Data Let method would parse the individual lines to assign the
the other properties. That would help to move that parsing code out into a
class where it can be better maintained, while also freeing up a few duties of
your main line code...
LFS
.
- References:
- variable size record length file parsing
- From: Matt Williamson
- Re: variable size record length file parsing
- From: Mike Williams
- Re: variable size record length file parsing
- From: Matt Williamson
- Re: variable size record length file parsing
- From: Jeff Johnson
- Re: variable size record length file parsing
- From: Matt Williamson
- variable size record length file parsing
- Prev by Date: Re: variable size record length file parsing
- Next by Date: Re: a self deleting program
- Previous by thread: Re: variable size record length file parsing
- Next by thread: Re: variable size record length file parsing
- Index(es):
Relevant Pages
|