Re: MI Undocumented (revisited)

[Gary Schwartz]

I can share with you some not very useful information about the "Hoover" functions from the years I spent working for Claritas.  Claritas was building a product that became nicknamed Hoover (I suppose it was meant to be some sort of data vacuum! - anyways I definitely remember a very loud sucking sound ;->) that used MapInfo Professional for its mapping engine (for Claritas' sake I won't disclose the product's actual name).  They struck a deal with MapInfo to include some special functionality for this product and the functions you found were written to support that.  I honestly can't remember what they do (it's been at least 4 years now since I worked on that product) and even if I could I'm sure that information would be considered confidential.  But I'm pretty sure that they're really not all that interesting.  My gut feeling is that they were put in to simplify the way commands were passed between the two products.  In those days we were still using DDE which was pretty slow, so I think they might have been added to reduce the number of DDE calls that had to be sent back and forth. Hope this sheds a little light on your mystery.  Let me know if you do figure out exactly what they do. Gary.   Anssi Joutsiniemi wrote: Functions: SetHooverInfo(strDummy,strDummy)GetHooverInfo(strDummy)HooverCommand(strDummy)