|
I beg to differ. MapInfo Pro knows exactly what records and fields and graphical objects have been edited at any time. The only thing MapInfo Pro's not good at, is making this information available to everyone else. The illusive "transaction files" (TDA, TIN and TMA) contains the information of what edits have been made. Only problem: they're locked when they exist, and deleted when closed. Otherwise I think it would be perfectly feasiable to utilize these to generate an audit trail of some kind. I'll make a simple feature suggestion for MI Pro 9.0 : have Pro add some log of all edits to a <table name>.log whenever edits are committed. The log file should be in a known, dense, maybe binary, format that could be utilized programmatically. Maybe just rowid+field+timestamp. And add an option to turn this feature on. That said, I too think a more server based approach would be a smarter option for a number of reasons, although I'm sure Oracle isn't the only egg in that basket. Best regards / Med venlig hilsen Lars I. Nielsen GisPro Peter Horsbøll Møller wrote:
|
_______________________________________________ MapInfo-L mailing list [email protected] http://www.directionsmag.com/mailman/listinfo/mapinfo-l
