John Colby
jwcolby at ColbyConsulting.com
Tue Oct 18 09:50:55 CDT 2005
LOL, yep. And that is exactly why a table driven method is my goal. You want delimited? NO PROBLEM. You want Fixed width? NO PROBLEM. You want fixed width delimited? NO PROBLEM. You want fries with that? Some idiot is going to ask for it. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Tuesday, October 18, 2005 10:31 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Re-Invent The Wheel?? On 18 Oct 2005 at 9:38, John Colby wrote: > Gustav, > > I certainly appreciate the "hard code" approach, I have doe that > myself. OTOH, I have had a handful now that were fixed formats but > needed "adjustments" to get it just right. For example: > > I am working on an export (and later an import) to the US government > for what is called PlanD, having something to do with medicare > re-imbursements to the city government. The upload specification is > VERY loosely defined, basically they say "fixed width (with field > widths specified), comma delimited, with no header (field name) line, > then they specify the format inside of date fields to be YYYYMMDD. > And THEN they say "if there is no data then you don't need anything in > that field, but the commas must exist. Yep, that certainly answers my question about whether there is such a thing as a fixed width, delimited file :-) -- Stuart -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com