Title: Auditing edits made to mapinfo tables.
Lars,
 
You are absolutely right. MapInfo certainly known the changes.  The problem is - as you write yourself - that these information aren't made availeble in any way.
 
The idea of a log-file is great. I would like to add another request, a RowEditedHandler that could be "caught" within your MapBasic application. This should be seen as a sort of trigger, so maybe we actual need as well a before as an after trigger.
 
Within these it should be possible to detect which column was updated.
 
So what we actual are asking for is a full support for "triggers" thru the MapBasic interface ?!
 
And you are right Oracle is just one of the possibilities. But for now, if you are using MapInfo, I can only see a few.

Peter Horsbøll Møller
GIS Developer, MTM
Geographical Information & IT
 
COWI A/S
Odensevej 95
DK-5260 Odense S.
Denmark
 
Tel     +45 6311 4900
Direct  +45 6311 4908
Mob     +45 5156 1045
Fax     +45 6311 4949
E-mail  [EMAIL PROTECTED]
http://www.cowi.dk/gis


From: Lars I. Nielsen (GisPro) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 04, 2006 2:49 PM
To: mapinfo-l@lists.directionsmag.com
Cc: Peter Horsbøll Møller; Mathew Linnane
Subject: Re: [MI-L] Auditing edits made to mapinfo tables.

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:
Mathew,
 
MapInfo isn't that good at these kind of things, not when working in the native tab format. You would need to write your own tools for doing all the operations - that would be quite a job.
 
I would recommend using a Spatial Database in stead. You can then make the database system keep track of all the changes, even tore them in a separate table, so that you have access to the previous version of every record.
 
MapInfo 8.0 introduced support for Oracle Workspaces. This is actual exactly what you are looking for. You can setup a table to keep track of every change, and this can be done from within MapInfo. The changes at stored in a separate table that with a small amount of work can be opened and viewed in the map as well.
 
Peter Horsbøll Møller
GIS Developer, MTM
Geographical Information & IT
 
COWI A/S
Odensevej 95
DK-5260 Odense S.
Denmark
 
Tel     +45 6311 4900
Direct  +45 6311 4908
Mob     +45 5156 1045
Fax     +45 6311 4949
E-mail  [EMAIL PROTECTED]
http://www.cowi.dk/gis
 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mathew Linnane
Sent: Tuesday, July 04, 2006 1:10 AM
To: mapinfo-l@lists.directionsmag.com
Subject: [MI-L] Auditing edits made to mapinfo tables.

I need to create an audit trail of all edits made to a certain mapinfo table. The Audit trail must include user ID, Date, Time etc. Can mapinfo facilitate any form of auditing? All ideas would help.

Regards,

 

 

 

Mathew Linnane

 

GIS/LIS Assets Officer.

Queanbeyan City Council.

257 Crawford Street

Queanbeyan NSW 2620.

Bus: (02) 6298 0205

Fax: (02) 6297 4044

Mob: 0412 565 552

Email: [EMAIL PROTECTED]

 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

"This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of Queanbeyan City Council, unless otherwise stated.

For the purposes of the Copyright Act, the permission of the holder of copyright in this communication may be taken to have been granted, unless stated otherwise, for the copying or forwarding of this message, as long as both the content of this communication and the purpose for which it is copied or forwarded are work related."

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 


_______________________________________________ MapInfo-L mailing list MapInfo-L@lists.directionsmag.com http://www.directionsmag.com/mailman/listinfo/mapinfo-l
_______________________________________________
MapInfo-L mailing list
MapInfo-L@lists.directionsmag.com
http://www.directionsmag.com/mailman/listinfo/mapinfo-l

Reply via email to