Hour() Function acting strangely - or not at all [datepart("h") vs hour()]

[dcdimon]

Okay, I've got some weirdness going on in my vba script and I'm not sure why. I have a script that is comparing the hour that is hardcoded to a form against the hour of the current time.

me.FormHrtxt = Hour(now())

If it is equal then other script runs, if not then nothing happens and the page is locked. It works fine in my development version of the database. However, when I import the script into the user version of the database, which is essentially the file I made the development copy from, it no longer functions as expected.

In normal scripting the Hour function shows as what I just typed - the word hour with a capital H. In the user database the hour function has changed to the word hour with a capital H and O - it now looks like this in the script HOur(Now()). I'm getting alternating error messages when the page loads/script runs. Either 'datatype mismatch' or 'can't find field HOur in expression'. I have no idea why this is happening. Older script that has the Hour() function in it now shows HOur() as well - but those seem to be working alright.

I've modified the newer script I brought over to use the Datepart() function:

Datepart("h",(Now())

So it's working as intended, but I am at a loss as to why the Hour() function is no longer running as expected. My initial assumption is that the dbs is corrupted somehow. I did try opening a blank dbs and importing over the components of the original and I found the same issue. However a new database without the import sees the Hour() function correctly.

It's all a bit maddening - and caused me quite a bit of cursing until I changed over to the Datepart() function. Has anyone ever experienced this problem? Any ideas? Or should I just chalk it up to the Access gremlins?

Thanks,
DD

[RuralGuy]

It is acting like you have your own HOur() function defined somewhere.

[pbaldy]

My first thought is that there may be a field/control/user function with that name, and Access is confused about which you're referring to. I'd hunt for that.

[pbaldy]

Oops, sorry Allan, slow typing on an iPad.

[John_G]

Hi -

A couple of things to look for:

There is a form with a control named "HOur" on it, and Access is confused as to ehat is being referred to or
There is a function or sub called "HOur" in a code module, and if it is in a form module, you won't always get the error.

You could check the second one by doing a whole-project search for "Sub HOur" or "Function HOur" with the Match Case option on. Even a search for just "HOur" might work if you use match case.

HTH

John

PS Sorry guys - your posts wern't there when I strted the reply! At least we're all on the same page!

[dcdimon]

Hi All,

I thought of that when I saw that it was changing the Hour to HOur. I did a whole project search for "HOur" by case and "Function HO" and found nothing.

I didn't think about looking for a control with the HOur name though.

There are several people working on this database - design phase - so occasionally we get some weirdness because of that. However, these forms were designed by someone that knows not to use Date, Time, Hour..etc as the name of anything because they're reserved for Access.

I'll try searching again and look at the controls. Because the syntax is changing, I really think it's a function issue, I just don't know where it is.

Thanks for the help,

DD

[RuralGuy]

You could also try *importing* the stubborn DB into a fresh new db and see if the problem follows. It might just be some corruption.
http://www.btabdevelopment.com/ts/impnew