bang head here
Member
Is this error any different in NET as is was in classic ASP? Im getting it now and tried the permission route that worked in the past, with no luck. Does anyone know if MS made this stupid error more of a blanket than it was in the past?
Thanks.
Thanks.