For filePro and overall strength which is best, SUSE or RedHat?

[Walter Vaughan]

Lerebours, Jose wrote:
> I am planning on using PHP or Perl (or both) to push data
> from filePro to MySQL.  Of course, if I can import 
> directly from MySQL and have scheduled tasks that will be
> even better, hence, I have never used MySQL.

You might want to look at postgreSQL instead of mySQL. Even though mySQL 
version 5 is going the way of a normal SQL server with triggers, 
postgreSQL is quite mature, whereas triggers are still alpha quality on 
mySQL.

Why would triggers be important? Because eventually *somebody* is going 
to want to update records in that remote SQL database and you're gonna 
be pulling hair out getting the changes back into filePro.

With triggers you can setup business rules that would create exports 
that you could use to sync the data back into filePro.

mySQL = fast, good for dynamic web page generation
postgreSQL = slower, better for accounting type apps

Why give up speed? If a field changes content, you want to have some 
sort of processing to kick off, in this case if a field changes content 
you want to update your filePro files with the change.

Or you can take the $50,000 that it would probably cost to legally 
license 600 various users and toss that at fpTech and get them to work 
on the alluded-to "New fpAPI"[1] that was mentioned at the Orlando '03 
convention and be able to use perl or php and talk natively to filePro.

--
Walter
[1] I bought a copy of Empire Data's fpAPI, but alas it only works with 
4.1 and earlier type indexes. I never did understand why it never was 
fully developed to work with 4.5 indexes.