Elizabeth.J.Doering at wellsfargo.com
Elizabeth.J.Doering at wellsfargo.com
Fri Jun 20 14:28:59 CDT 2008
Because it is on the .update line, browse through the table you are updating, looking for nasty corrupt records there. Or, try doing a make table query to write your target table into a new temp table. If you have a corrupt record, the make table query will more than likely fail, maybe with a helpful message of some kind. HTH, Liz Liz Doering Systems Engineer Technology Information Group elizabeth.j.doering at wellsfargo.com 612.667.2447 (o) This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of McGillivray, Don [IT] Sent: Friday, June 20, 2008 1:48 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Error 3001 - invalid argument - What the . . . . ? Hmmm. I'll check, but don't think so. If that were the case, wouldn't I expect the error to occur at the line where I attempt to assign the value, rather than the .Update line? -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A Matte Sent: Friday, June 20, 2008 11:41 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Error 3001 - invalid argument - What the . . . . ? Is there possibly a null being passed? Mark A. Matte > From: Donald.A.McGillivray at sprint.com> To: accessd at databaseadvisors.com> Date: Fri, 20 Jun 2008 13:28:12 -0500> Subject: [AccessD] Error 3001 - invalid argument - What the . . . . ?> > Out of the blue, I'm getting the above error (minus the "What the . . .?") in a proc that has been running rock solid forever. It's in a block of code where I'm using DAO to write a record to a table:> > .AddNew> !field1 = SomeValue1> !field2 = SomeValue2> .Update> > Code is puking on the .Update line.> > I suspect some sort of corruption, but all my usual remedies (decompile/recompile, compact/repair) don't seem to be having any effect. This is probably my weakest area of understanding with Access, etc., so I'm not even sure I'm using those approaches correctly.> > Hoping somebody might be able to suggest a more reeliable way to the problem . . . .> > Don McGillivray> > > -- > AccessD mailing list> AccessD at databaseadvisors.com> http://databaseadvisors.com/mailman/listinfo/accessd> Website: ! http://www.databaseadvisors.com _________________________________________________________________ The other season of giving begins 6/24/08. Check out the i'm Talkathon. http://www.imtalkathon.com?source=TXT_EML_WLH_SeasonOfGiving -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com