Export Data to a File Weirdness

Kenneth Brody kenbrody at bestweb.net
Wed Apr 6 12:30:15 PDT 2005


Quoting DataDoIt (Wed, 6 Apr 2005 14:32:56 -0400):

> fPODBC v1 on Win2k3 Server;
[...]
> SYSTEM "ECHO " & variable & " >> file.csv"
[...]
> In the development version of the data, the export works perfectly.  The
> order of events are:
>
> 1. Deletes the file that's already there using:
>    SYSTEM "DEL file.csv"
>
> 2. Exports out a header routine that sends out the column headers using:
>    SYSTEM "ECHO " & header & " >> file.csv"
>
> 3. Finally exports out the data using the above.
>
> On production, it'll remove the file okay.  It'll write the header info
> okay, but won't write the data.  I've verified that there's data in the
> variable.  What in the world could this be?  The only difference is
> filePro data folder on the same machine.

The only difference the current directory would make is the location
of the resulting file, and whether or not you have permissions to
create and/or write to the file.

I assume that "it'll write the header info okay" means that step (2)
above causes the file.csv file to contain a single line consisting of
the data in the variable "header".

By "won't write the data", I assume you mean that the line(s) consisting
of the variables in subsequent SYSTEM "echo ..." lines do not end up in
the file.

Is that correct?

Can you give a specific example, including the complete, exact, statement
used for the export, along with the complete, exact, contents of any
variables referenced in the SYSTEM command?

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com


More information about the Filepro-list mailing list