Susan Harkins
ssharkins at gmail.com
Mon Mar 19 15:52:26 CDT 2012
BTW -- I'm sorry, I should've sent this in the original message instead of sending a second message. If you can copy the sql statement into a query window and run it from there -- you might get a much more specific error message. Susan H. > <http://msdn.microsoft.com/en-us/library/bb178105(v=office.12).aspx> > > That's not terribly helpful, but since this started after you moved, that > last item -- the network issue -- could be the problem. > > <http://support.microsoft.com/kb/305617> > > That one seems to help pinpoint a possible problem, although it doesn't > actually specify the error number, so it might not be related at all. I > probably haven't helped at all. But, you might consider rewriting the save > procedure and bypass it altogether -- stuff like this can drive you nuts. > > Susan H. > > >> >> The research I've done on google hasn't led me anywhere. Have anyone >> seen >> this error before? Any hints for me on where I should focus my >> troubleshooting efforts? >