Reading from Standard In/Writing to Standard Out? (on Solaris)

[Walter Vaughan]

Tim Fischer wrote:

> I've got a situation where I need to keep a mysql database in sync with our
> FilePro database.  Our idea is to use Standard in/out as a medium to
> transfer data.  I don't know, however, to get FP to read to standard in or
> write to standard out.

The easy answer is to use fpODBC on WindowsXP and dump Solaris.

However, you really haven't described the problem, since several
band-aids exist depending upon your goals/expecations.

Are you talking about a single table in a MySQL database staying
in sync with a filepro file? Or are you talking about multiple filePro
files?  Does the MySQL table have updated field data that needs to be
moved back to the filePro?

Is this something that would be best served by running a report that:
	1) Writes an SQL text file
	2) Flushes the MySQL table
	3) Loads a new MySQL table from the SQL text file

Or are you looking for something on a record level that would
do something similar to the above but for single records?

<Question for hardcore "automatic" processing table experts>
	Is there a way to detect in automatic processing that the
	which pass is occurring... before you enter the record and
	after you are leaving the current record?
</q>

How would you even deal with the issue of popup-update and updates
to files via lookups?

This is NOT a simple issue, and the fact that fpODBC will not exist
for Unix OS's in the near future is cause for reflection as to what
is your long term filePro strategy.

What's the end game.

If you are just wanting to expose filepro data via a browser, Howie's
fpWeb might be a much better solution. Or fpCGI. Or just wrap filepro
with perl and use a cgi-bin script. Or Mark's ONE-GATE.

--
Walter
    ...who's trying to decide all of the above...