Jump to content

Douglas Husemann

Members
 View Profile  See their activity

  • Content count

    2

  • Joined

  • Last visited

Posts posted by Douglas Husemann

  2. Posted · Report reply

    I understand why multi-lingual users need unicode, but I chose this tool so that I could hook on to the data with an ODBC driver and report on it any way I wanted. Unless WG is contemplating moving to an Oracle DB (which by the way will make the cost go up significantly maybe 20 times), I'd hate to see them change the database format.

     

    Marcie,

     

    There are several freely available databases (besides Oracle) that support Unicode, ODBC and JDBC interfaces, known names like mySQL, PostgrSQL and others. Some of them may also be embedded into the program.

    since when did mySQL start supporting Unicode?? I had been following Unicode in databases for awhile now and as of 5.0 mySQL didn't support Unicode.

     

    But yes there are several other underlying database choices out there, the primary issue is the lack of a Data language that Foxpro offered.

     

    Even in the realm of MS you have SQL CE which can be embedded or SQL Server express, which would handle most data sizes that are encountered

    within TMG. (SQL Server Express has the same limitation on data size that Foxpro has for instance) both are free.

     

    In either case moving to a different underlying database would not be a small undertaking.

     

    Foxpro also offered its own windowing system. Which some have noted doesn't necessarily follow the underlying changes in the OS or common in usage systems.

     

    So replacing Foxpro would be a three fold undertaking. Replacing the language, replacing the windowing system (yes I am aware there are several features in TMG

    that extend the Foxpro) and replacing the database. (that said Foxpro provides provisions to talk to other databases besides dBase which is the base of the foxpro

    database system)

     

    So in other words a complete rewrite of TMG.

     

    (and I can think of much better database interfacing mechanisms than odbc but that is a different topic all together)

     

    Douglas

×