[AccessD] Error 3001 - invalid argument - What the . . . . ?

Thanks, Susan

My recordset object is declared explicitly as a DAO recordset, and the code is called only when there is something to add to the table and valid values have been passed to the proc.

Since this has been running solid for so long, I really suspect some sort of corruption, but restoring a previous version of the front end didn't solve the problem.  DLL corruption perhaps?  But which one?  And how to fix?


-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Friday, June 20, 2008 11:49 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Error 3001 - invalid argument - What the . . . . ?

I was wondering about the same thing sort of -- are you sure there's
actually something to update?

Also -- I can't remember the error when there's an ambiguity between DAO and
ADO -- so I'd check the references just to make sure the right library's
set.

Susan H.



Is there possibly a null being passed?


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com