Peculiarities of FHX Editing

I came across this blog post, One of the many peculiarities of fhx editing on the JDYOUNGB blog and thought I'd pass it along. He notes:

When using a development system along with a live system, keeping all your paperwork synced up can be a nightmare. However, being familiar with fhx's can help make this much easier and will let you ignore certain differences between development exports and live exports.

Feel free to add your thoughts to his points below.

2 Replies

  • Reverse engineering fhx files has been a necessary evil for most users.  I'd like to see some of this pain eliminated by either

    1. Utilizing XML as the import/export format to allow XSL to be used for interoperable and easy comparison, querying, documentation generation, import generation, offline database generation etc.; no more authoring custom parsers.  

    2. Make available an SDK for producing customized objectivity database clients that utilize SQL-like functions for reading (and maybe writing) the control database extensibly.  This would certainly be preferred to hacking export files.

  • In reply to Youssef.El-Bahtimy:

    I faced a project challenge like this recently as well and it was a very painful exerience and I wasn't very happy with it when I was done after all.  I would love to see some tools like this developed.

    Brian McWhorter ISA:CAP OPC:SI PE:CSE