RE: [MI-L] Auditing edits made to mapinfo tables.

2006-07-04 Thread Terry McDonnell
Title: Auditing edits made to mapinfo tables.



Mathew 

 
Well all I can offer is what seems to be obvious.  
Create a table that holds all the audit trail fields and create new records for 
it every time you amend the database.  If you keep your updates to the 
database in dedicated procs then that would be the place to also update the 
audit table.
 
Regards
 
Terry 
McDonnell


From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of Mathew 
LinnaneSent: 04 July 2006 06:00To: Terry 
McDonnellSubject: [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


RE: [MI-L] Auditing edits made to mapinfo tables.

2006-07-04 Thread Peter Horsbøll Møller
Title: Auditing edits made to mapinfo tables.



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 
LinnaneSent: Tuesday, July 04, 2006 1:10 AMTo: 
mapinfo-l@lists.directionsmag.comSubject: [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


Re: [MI-L] Auditing edits made to mapinfo tables.

2006-07-04 Thread Mike Tonge
You could try writing a little mapbasic program that you use instead of the open file command.  Then each time the file requiring auditing is opened you could update another table with the date, time and username (accessible through windows api) of the person editing the file.
 
If you want any more info on this idea please e-mail me.
 
Mike
- Original Message From: Terry McDonnell <[EMAIL PROTECTED]>To: Mathew Linnane <[EMAIL PROTECTED]>; mapinfo-l@lists.directionsmag.comSent: Tuesday, 4 July, 2006 9:31:56 AMSubject: RE: [MI-L] Auditing edits made to mapinfo tables.
Mathew 
 
Well all I can offer is what seems to be obvious.  Create a table that holds all the audit trail fields and create new records for it every time you amend the database.  If you keep your updates to the database in dedicated procs then that would be the place to also update the audit table.
 
Regards
 
Terry McDonnell


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mathew LinnaneSent: 04 July 2006 06:00To: Terry McDonnellSubject: [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 listMapInfo-L@lists.directionsmag.comhttp://www.directionsmag.com/mailman/listinfo/mapinfo-l
___
MapInfo-L mailing list
MapInfo-L@lists.directionsmag.com
http://www.directionsmag.com/mailman/listinfo/mapinfo-l


Re: [MI-L] Auditing edits made to mapinfo tables.

2006-07-04 Thread Lars I. Nielsen (GisPro)
Title: 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 .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


RE: [MI-L] Auditing edits made to mapinfo tables.

2006-07-04 Thread Peter Horsbøll Møller
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 
PMTo: mapinfo-l@lists.directionsmag.comCc: Peter Horsbøll 
Møller; Mathew LinnaneSubject: 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 .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 LinnaneSent: Tuesday, July 04, 2006 1:10 
  AMTo: mapinfo-l@lists.directionsmag.comSubject: 
  [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 communi

Re: [MI-L] Auditing edits made to mapinfo tables.

2006-07-04 Thread nicholas . g . lawrence
> Lars I. Nielsen said
>
> I'll make a simple feature suggestion for MI Pro 9.0

Just how do we make feature suggestions for MapInfo?

Does MapInfo read this list?

Is there a place on the MapInfo web site where feature suggestions can be
logged?

Does MapInfo have a contact person who can be emailed suggestions?

Once submitted, do suggestions have a tracking number? Can we track their
progress?

nick



Opinions contained in this e-mail do not necessarily reflect
the opinions of the Queensland Department of Main Roads,
Queensland Transport or Maritime Safety Queensland, or
endorsed organisations utilising the same infrastructure.
If you have received this electronic mail message in error,
please immediately notify the sender and delete the message
from your computer.

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


Re: [MI-L] Auditing edits made to mapinfo tables.

2006-07-04 Thread Richard Greenwood

On 7/4/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:


Once submitted, do suggestions have a tracking number? Can we track their
progress?


They don't even let us users track bugs, let alone feature requests!
It really discourages user participation. All MI wants from us is our
credit card number.

Rich

--
Richard Greenwood
[EMAIL PROTECTED]
www.greenwoodmap.com
___
MapInfo-L mailing list
MapInfo-L@lists.directionsmag.com
http://www.directionsmag.com/mailman/listinfo/mapinfo-l


RE: [MI-L] Auditing edits made to mapinfo tables.

2006-07-05 Thread Peter Horsbøll Møller
Rich,

I have to disagree here. Many of the improvemnets that has been made during the 
last versions of MapInfo Pro have been made because users have asked for them.

The best way to make MapInfo aware of you wish is to send the wish to your 
MapInfo contact person. This may be a MapInfo Partner or a person at MapInfo 
Corp.

For MapInfo Pro wishes I would recommend either Moshe Binyamin for the US 
region and Tom Probert in the EMEA region. 

Just to mention a few improvement that could have been a result of 
questionlately on the list:
- Move a layer from one map to another
- Combine two maps into one
- Improved printing engine. The 28000 pixel limit is gone
- Larger number of points in buffer (from 100 to 500)
- Preference for area and distance units
- Copy text from message and statistic window
- GeoPrinter included on installation cd
- Server Refresh button works on Live tables as well as Linked

These might look as huge improvements, but for the daily user, they are very 
helpfull.

So, remember to let MapInfo know what you need.

Tracking is a different story. I can see why they don't want to publish their 
problems and list of new ideas to the public.

And of course do MapInfo like to have your money. Otherwise they wouldn't exist 
anymore.

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

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Greenwood
Sent: Wednesday, July 05, 2006 3:08 AM
To: [EMAIL PROTECTED]
Cc: mapinfo-l@lists.directionsmag.com
Subject: Re: [MI-L] Auditing edits made to mapinfo tables.

On 7/4/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:

> Once submitted, do suggestions have a tracking number? Can we track 
> their progress?

They don't even let us users track bugs, let alone feature requests!
It really discourages user participation. All MI wants from us is our credit 
card number.

Rich

--
Richard Greenwood
[EMAIL PROTECTED]
www.greenwoodmap.com
___
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


RE: [MI-L] Auditing edits made to mapinfo tables.

2006-07-05 Thread Rex Ballard
Title: Auditing edits made to mapinfo tables.



Great 
idea, if MapInfo Corp are willing to consider the change.  Can I suggest 
that the previous value (the value being overwritten) is also recorded - 
that would be almost as good as a full 4-dimensional database and would allow 
recreation of tables at any point in the database's history as well as providing 
the audit trail.  It should also allow "rate of change" analysis without 
the need for discrete time slices which will always be a compromise between 
flexibility and storage space.  Imagine being able to show the spread of 
disease with respect to the timing of some other factor such as weather, food 
imports, water quality or other datasets.
 
With 
regard to a server based approach, I have (in a previous position) used MapInfo 
Spatialware with SQL Server and tried saving all transactions.  With five 
full-time GIS operators and another four officers maintaining their section's 
data as part of their duties, it didn't take too long before the transaction 
file began to have a serious effect on system storage and backup 
performance.
 
Regards
Rex 
Ballard

  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED]On Behalf Of Lars I. 
  Nielsen (GisPro)Sent: Tuesday, 4 July 2006 8:49 PMTo: 
  mapinfo-l@lists.directionsmag.comSubject: 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 .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 LinnaneSent: Tuesday, July 04, 2006 
1:10 AMTo: mapinfo-l@lists.directionsmag.comSubject: 
[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 th

Re: [MI-L] Auditing edits made to mapinfo tables.

2006-07-05 Thread Richard Greenwood

On 7/5/06, Peter Horsbøll Møller <[EMAIL PROTECTED]> wrote:

Rich,

I have to disagree here. Many of the improvemnets that has been made during the 
last versions of MapInfo Pro have been made because users have asked for them.

The best way to make MapInfo aware of you wish is to send the wish to your 
MapInfo contact person. This may be a MapInfo Partner or a person at MapInfo 
Corp.

For MapInfo Pro wishes I would recommend either Moshe Binyamin for the US 
region and Tom Probert in the EMEA region.



Peter,

Thanks for your comments, your positive attitude, and your many help
posts to the list.

I have used MapInfo Pro since version 3.0 and consider it to be a very
good product. Over the years I have run into various bugs and
communicated them thru my MI Business Partner, and directly to Moshe
B. on a couple occasions.

Personally, I have been disapointed with the ressponse I received. I
can remember only one occasion in which a bug was fixed mid-release
(and this was a bug that I had reported in the previous release).

Many projects use Bugzilla which allows users to track the progress of
bug fixes, place feature requests, and receive notification upon
resolution. It is a far more satisfying experience when a user fells
that their input is tracked and respected, rather than having to plead
with  a reseller (Business Partner) who may or may not fully
comprehend your problem, or get a direct dialog with a senior
engineer.

My point, which may have come off with an overly cynical tone, was
that MapInfo has done little encourage my participation in the
improvement of their product. Lest I start a flame war, I will leave
it at that.

Rich

--
Richard Greenwood
[EMAIL PROTECTED]
www.greenwoodmap.com

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


RE: [MI-L] Auditing edits made to mapinfo tables.

2006-07-05 Thread Peter Horsbøll Møller
Rich,

I agree with you on this point. MapInfo hasn't been very good at giving 
feedback to the person entering the problem. I think this is simply because 
they didn't track that information. They didn't know who send in the bug or 
feature request.

But I also think this is changing. They have implemented a new system for - at 
least feature requests - where the request is connected to a name and a email 
address. This should give them the possibility to contact the person who send 
in the request and even ask for more detail.

I must admit that I still need to see that part work ;-) But they seem to be 
heading in the right direction.

When you get a bug reported, you should get a bug number. This can be used to 
track the bug, not interactively on a web site, but fore instance via email.

But you are right. It is a serious problem for MapInfo, if their costumers 
don't feel that they are heard. Especially as MapInfo keep saying that they 
want to listen to the costumers.

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

-Original Message-
From: Richard Greenwood [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 05, 2006 11:55 PM
To: Peter Horsbøll Møller
Cc: mapinfo-l@lists.directionsmag.com
Subject: Re: [MI-L] Auditing edits made to mapinfo tables.

On 7/5/06, Peter Horsbøll Møller <[EMAIL PROTECTED]> wrote:
> Rich,
>
> I have to disagree here. Many of the improvemnets that has been made during 
> the last versions of MapInfo Pro have been made because users have asked for 
> them.
>
> The best way to make MapInfo aware of you wish is to send the wish to your 
> MapInfo contact person. This may be a MapInfo Partner or a person at MapInfo 
> Corp.
>
> For MapInfo Pro wishes I would recommend either Moshe Binyamin for the US 
> region and Tom Probert in the EMEA region.


Peter,

Thanks for your comments, your positive attitude, and your many help posts to 
the list.

I have used MapInfo Pro since version 3.0 and consider it to be a very good 
product. Over the years I have run into various bugs and communicated them thru 
my MI Business Partner, and directly to Moshe B. on a couple occasions.

Personally, I have been disapointed with the ressponse I received. I can 
remember only one occasion in which a bug was fixed mid-release (and this was a 
bug that I had reported in the previous release).

Many projects use Bugzilla which allows users to track the progress of bug 
fixes, place feature requests, and receive notification upon resolution. It is 
a far more satisfying experience when a user fells that their input is tracked 
and respected, rather than having to plead with  a reseller (Business Partner) 
who may or may not fully comprehend your problem, or get a direct dialog with a 
senior engineer.

My point, which may have come off with an overly cynical tone, was that MapInfo 
has done little encourage my participation in the improvement of their product. 
Lest I start a flame war, I will leave it at that.

Rich

--
Richard Greenwood
[EMAIL PROTECTED]
www.greenwoodmap.com



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