"Does it happen just after you create the connection without no query execution?"
Yes, but I think technically, Access does a query just to setup the table so that is when it crashes the server.
The DSN is through a mapped network drive to the remote database path. It was not a valid MAX attached database. So It may have been this bastardized setup. Although the mapped drive had permissions, the machine did not have permissions that it would need to go through "MAX" because the machine was not a member of the domain, so automatic user authentications would be rejected.
I will try with a remote machine that is a domain member and would therefore pass all appropriate permissions using MAX to attach the data source. I will also try to recreate the crash using the domain machine.
I also had nicitdl5 hang tonight during a simple client hypertrend trace-back a few days of data. I could see where the data stopped being sent by the missing trace endpoints on the trend. After recovery on the server, I tried the exact same hypertrend trace-back and this time it was fine. Citadel still needs some stability work!!!
Ed
