DATE() issue

  • Thread starter Thread starter wwaiter
  • Start date Start date
W

wwaiter

I have an access 2000 database that is shared amount 15
people with 15 pc's. It appears to work well with one
exception... Three out of the 15 people, recieve an error
message when they launch the database from the network.

The error message reads:
"The following expression cannot be used in this
statment... possibly due to Lbound, Ubound, SPC, etc..."

In addition, the calendor control that I've added to the
main form will not fully appear, and any forms that
contains a date() expression will not function properly.

Personaly, I belive the whole thing is linked to the date
() function as it exists in many of the forms as well as
the calendar control.

If you know how I could go about correcting these, your
assistance will be apprictaed.


Thanks
Waiter
 
Since it's working on some, but not all, machines, the first thing to
suspect is a References problem.

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target
machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)
 
Personaly, I belive the whole thing is linked to the date
() function as it exists in many of the forms as well as
the calendar control.
Click to expand...

This appears to be the very common References bug. Open any
module in design view, or open the VBA editor by typing
Ctrl-G. Select Tools... References from the menu. One of the
..DLL files required by Access will probably be marked
MISSING. Uncheck it, recheck it, close and open Access.

If none are MISSING, check any reference; close and open
Access; then uncheck it again. This will force Access to
relink the libraries.
 
I did exactly what you said and it appears that the
machines where missing the following OCX file.
MSCOMCT2.OCx.

I've updated the machines with this file, and all works
well now, with the exception that the calendar control
will not display properly. Any thought on that one?


Your assistance is greatly appreciated.
 
I had an Employee Scheduling db in
Access 2000 where I thought I'd try
the calendar and the users thought it
was great.

Then I tried to run on an Access 2002
machine. I was limited in time to give to it,
but eventually got frustrated and gave up.

I rate OCX's right up there with committees!
 
Back
Top