Hi Paul.

Both of the dbfs that you mentioned are located in a central place on each clients file server. All users at a particular location should be getting this error unless security rights are different. We now believe that this error is happening because of network problems (imagine that <g>). The client is installing new network hardware as soon as the equipment arrives (switching from hubs to a router) so we'll see if these errors go away.

Thanks.

Dan

>>Only a couple of our users are reporting "File does not exist." errors when exiting our MM app. Has anyone come across this yet? I think it is coming from the reset method in the globalenvironment but I'm not sure. Unfortunately, the error manager is disabled before the reset is run.
>>
>>TIA
>>
>>Dan
>
>Hmm...I think I ran into this once when I was missing one of the tables that needs to be in the main app directory (eg. classes.dbf, string.dbf, etc.).