It's not an Access problem.. it's DisplayDataMap.

It will kick out that error if *any* of the parameters are incorrect or don't match what it expects..

My stock answer is to read the sections in "Programming MapPoint in .NET" as I always go back and refer to it when I am working with DisplayDataMap myself...

I keep thinking I should create a guide or article on DisplayDataMap on MP2Kmag.com but I haven't gotten around to it.

Eric

__________________