Invalid procedure call or argument

[kimmer6160]

I have one user that is unable to run a VBA procedure. She is the only one and the error she receives is Invalid procedure call or argument. I found at the Microsoft website that if she is receiving that message then she is missing a reference but I have checked and she is not. I even replaced all reference files to be sure there wasn't a corrupt one. I am still receiving it. Any ideas why? Help! Thanks!

 

[ghudson]

It still sounds like a missing referrence. What errors when you try to compile the db on that users PC?

 

[kimmer6160]

There are no errors when I compile it. It compiles just fine. That is what is so confusing.

 

[Kodo]

what MDAC version are you referencing? and what MDAC version does the problematic PC have on it?

 

[kimmer6160]

I am sorry to sound stupid but how do I found out what the MDAC version is?

 

[Kodo]

the latest version of the Data Access technologies (including the Jet driver ) from MS can be found here

http://msdn.microsoft.com/data/downloads/updates/default.aspx

WinXP default is MDAC 2.7

MDAC checker is here
http://www.microsoft.com/downloads/...F6-4A21-4B43-BF53-14332EF092C9&displaylang=en

 

[kimmer6160]

Ok. Did all of the updates on the problem PC and it is still doing it! Now I have figured out that it is not all the time it is only with certain records. I don't see anything different or unusual about the record.

 

[Kodo]

it's probably not the record, but what you're doing with the record.

Is there anything particular about the records in question that you have chosen to write some function for processing that information?

i.e.

if record=x then 
    do y 'causing error?
else
    do nothing
end if