Bad references don't always make sense. If there is a bad reference, it may
not necessarily be in the dll that you're seeing the problem in. You may
even get what you're seeing, one function in a dll will work while another
won't, but the problem is one of the other references.
--
Wayne Morgan
Microsoft Access MVP
<(E-Mail Removed)> wrote in message
news:523a01c4911d$3d343fd0$(E-Mail Removed)...
>I thought it had something to do with the references
> also. I have determined that either/or makes use of VBA
> ref VBE6.DLL, ver 6.4.99.69 as indicated in the object
> browser.
>
> Harold Fairbanks
>
>>-----Original Message-----
>>Right off-hand it sounds like a problem with the
> References. Try the
>>information here to see if it helps.
>>
>>http://members.iinet.net.au/~allenbrowne/ser-38.html
>>
>>--
>>Wayne Morgan
>>Microsoft Access MVP
>>
>>
>>"Harold" <(E-Mail Removed)> wrote in
> message
>>news:514701c49111$c61a7230$(E-Mail Removed)...
>>> Private Sub Date_DblClick(Cancel As Integer)
>>> Me![End Date] = Date
>>> End Sub
>>>
>>> This code was originally written in Access 2000. I am
>>> developing in Access 2002 and attempting to use the
> same
>>> code. When installed and run on Windows 2000 server,
> the
>>> code errors thusly - Cannot find object
>>>
>>> If I change Date to Now, it works fine.
>>>
>>> I ran accross some knowledge base info that indicates
> the
>>> date function in 2000 requires the (), but access 2002
>>> actually drops these parentheses. In this case, the
>>> function is NOT treated as a function, but text (ie -
>>> "Date")
>>>
>>> Has any one else run into this problem and may be able
> to
>>> provide some help?
>>
>>
>>.
>>