>No. What we are seeing is a very long delay from the processing of FORM1.Load until when the Form appears on the screen.
Well, something is different for that user - the trick is finding out what that is ...
Another SWAG:
- Is that user getting a unique mapped drive (i.e. that other users aren't getting), and
- is that drive off-line or otherwise having access problems, and
- does your app have that drive in the path ahead of the drive where the data are actually located?
Or, does the user just have a path set with one or more large, slow-to-enumerate folder(s)?
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
