× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. November 2011

Re: FTP Format

Or use CPYFRMIMPF for some of those formats to parse them. CSV is the one that usually works - the others need special handling, right?


On 11/15/2011 10:54 AM, George Kinney wrote:
My question to the group is: Isn't
FTP just a character-by-character transmission? That is, the item
number
may be 1-5 numbers (1-99999). If only '1' is transmitted, would not
that
mean that everything gets PUT into the wrong locations of an SQL DDL
file on
our system in that case?
FTP isn't 'database aware' for sure, but it doesn't matter. You will be
receiving a file, not a transaction. (or maybe logically it *is* a
transaction, but it'll still be handled like any other file would be)

If the data records are sent in a fixed format, you can FTP them
directly into PFs with matching record formats and they'll be usable
as-is. We do this all the time.

If they are sent in a structured format, like CSV, XML, JSON, whatever,
then you'll have to parse them and then add them to the data base.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.