Hi Matt,

Are the maps being used on a Networked or Standalone installation? If it is networked, does the Object Sheet File Path for each client point to the same folder, and does the Map File Path point to a different local folder for each client? If the Object Sheet File Path is different, then that could certainly trigger resets. This can also happen if you have more than 1 Recorder 6 database installed, and you reconfigure your application sometimes to toggle between the two, but without ensuring that you have a different Map File Path and Object Sheet File Path for each database.

I have not experienced a read failure occurring as a result of the map being used "too fast". What sort of set up do you have? (i.e. how many background tiles, layers & polygons) We can then try to reproduce it.

Simon

Simon,

I adjusted the registry on that basis. And I think it will have cured some of the issues on the clients.
However, i still get regular reset demands when I try and import and manipulate polygons.

While its not totally consistent, importing an external polygon layer into my 'search' polygon layer is a gamble.  If I get away with it the first time, the chances of me getting away with it the second time is extremely slim.

I have about 8 active polygon layers. I dont keep the background layers in long enough to include them though we have about 40 covering the area.

The network isnt particularly fast and can stall, so maybe this is the weak point.

And we only run the one database.

Thoughts?

thanks

MAtt