I am having the strangest problem. I use the Date function in several
of my forms and modules in an Access 2000 mdb. Lately, wherever in my
code (in this one mdb) I use the Date function, it changes to date
(lower case vs proper case). I can fix this very temporarily by
reconstructing the database (importing all objects to a new mdb) or
using the decomplie option to open it. But in either case, once I
compile it reverts back to lower case. It does not seem to impact the
functionality of the function - in other words, it still works either
way. I have played with the references and they all seem fine. But I
do not seem to be able to get it to be using Date. I have other
databases that have many of the same modules and some of the same
forms etc and none of these other DB's are having the same problem
with Date vs date. They are all on the same computer.
The reason I care about this so much, since it does 'work' is that I
have developed a Version Control kind of system for myself to help
track changes as I develop, and to make it easy to know which objects
have changed and need to be propagated to other databases. Esentially
I create a Checksum for each object and save it in an Updates table.
At least once a day, I run my Version Control and it checks to see if
any objects have a new checksum and if so, updates the Update table
and prompts me for a comment to be saved alng with the latest Checksum
for the object. My checksum formula is case sensitive so I get a
different checksum for Date than for date and thus it makes it
impossible to compare objects across DB's since identical (except for
Date) objects get a different checksum.
Has anyone seen anything like this before? any suggestions? I guess I
could change my checksum algorithm, but it has been working ok for a
few weeks and I don't know why it has started doing this now. Any
insights? Ultimately, this is all an effort to get around the fact
that Access 2000 doesn't give me a nice way to know when objects were
last modified. So I have put a lot of time and energy into trying to
compensate with my own version control solution. I'm also interested
in knowing if there are any other solutions to this out there.
TIA,
Christine