Flakey =Date() in report 1

[Kubilus1]

Okay guys, this is a weird one I can't quite figure out. I will be as descriptive as possible.

Running office97 on windows 98SE.

On one report on just Some machines a text box with a control source of:
=Date()
will not work correctly. At first it told me 'The function you entered can't be used in this expression' when I try to create the text box. After updating to service pack 2b, I can create the text box, but when I run the report it asks me to enter a parameter for Date. The real funny thing it works right on one machine (my developement machine) which runs the same version of windows, office, and all service packs.

I tried creating a module with this code to test the Date function:

Public Function getDate() As String
Dim currDate As String
currDate = Date
Debug.Print "Date= " & currDate
getDate = currDate
End Function

On the malfunctioning machines it tells me 'Can't find Project or Library' highlighting the Date function on the third line. Copying this code to another access database and running on the same machine, it works fine.


Thanks for any help,

Matt

 

[Maquis]

It sounds like you are missing a library. On the bad PC, go to the Tools --> references option on the menu. (It will show up on the menu when you are in a VB code module).

The checked references will show at the top of the list and one of them may have "MISSING" in front of it. You can probably copy the .dll from the PC that works, or it may just be located in a different directoy on your PC. Maq
<insert witty signature here>

 

[Kubilus1]

Yes, a MISSING activeX reference. It is unnecessary for the program so I disabled, now everything works fine.
Apparently installing an ActiveX control for an explorer tree on my development computer caused some sort of take over of my other activeX stuff.

Thanks,
Matt