Janet Erbach
jerbach at gmail.com
Mon Mar 19 15:54:21 CDT 2012
Susan - I did try rewriting the save procedure for my custom form. Spent 2 hours converting all my code from looping through the records to posting the changes with queries. It made no difference - still got the same error, so I left that day pretty disgusted. Came back in the next morning - and it worked fine! I'll check the link you sent me. Janet On Mon, Mar 19, 2012 at 3:51 PM, Susan Harkins <ssharkins at gmail.com> wrote: > <http://msdn.microsoft.com/en-**us/library/bb178105(v=office.**12).aspx<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<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? >> > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/**mailman/listinfo/accessd<http://databaseadvisors.com/mailman/listinfo/accessd> > Website: http://www.databaseadvisors.**com<http://www.databaseadvisors.com> >