Age Converstion Problem

[Ken]

I have converted a 97 database to a 2000 database. The age conversion as
below has stopped working.

=DateDiff("yyyy",[D-O-B],Date())-IIf(Date()<DateSerial(Year(Date()),Month([D
-O-B]),Day([D-O-B])),1,0)

Even if I create a new field in the converted database, it still will not
work.
I then used 2000 to create a new database with a new table and form and
found that the age conversion now worked as it should.
I then used a small converted database and imported all of the date from it
to the newly created database, and the imported data worked apart from a
couple of errors showing On Click problems on buttons and some VBA problems.
After deleting buttons and re-createing them, the new database is now fully
working.

My main database (converted to 2000) is very complex and has multiple forms
(loads of buttons) and VBA functions, and although I imported the data into
a newly created database, (The age converstion now works OK) It will take
for ever sorting out the On click errors buttons and VBA errors.

The main problem is created during converstion to 2000.
Any one know of any fixes for either the Newly created or the converted
databases to overcome this problem.

Regards
Ken

 

[Douglas J. Steele]

Probably 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)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html


--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)

I have converted a 97 database to a 2000 database. The age conversion as
below has stopped working.

=DateDiff("yyyy",[D-O-B],Date())-IIf(Date()<DateSerial(Year(Date()),Month([D
-O-B]),Day([D-O-B])),1,0)

Even if I create a new field in the converted database, it still will not
work.
I then used 2000 to create a new database with a new table and form and
found that the age conversion now worked as it should.
I then used a small converted database and imported all of the date from it
to the newly created database, and the imported data worked apart from a
couple of errors showing On Click problems on buttons and some VBA problems.
After deleting buttons and re-createing them, the new database is now fully
working.

My main database (converted to 2000) is very complex and has multiple forms
(loads of buttons) and VBA functions, and although I imported the data into
a newly created database, (The age converstion now works OK) It will take
for ever sorting out the On click errors buttons and VBA errors.

The main problem is created during converstion to 2000.
Any one know of any fixes for either the Newly created or the converted
databases to overcome this problem.

Regards
Ken

 

[Ken]

Douglas

I am indebted to you as may others are.
There was a reference missing-utility.mda, after unticking it, all was OK.

Thanks again.
Ken

Probably 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)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html


--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)

I have converted a 97 database to a 2000 database. The age conversion as
below has stopped working.

=DateDiff("yyyy",[D-O-B],Date())-IIf(Date()<DateSerial(Year(Date()),Month([D

-O-B]),Day([D-O-B])),1,0)

Even if I create a new field in the converted database, it still will not
work.
I then used 2000 to create a new database with a new table and form and
found that the age conversion now worked as it should.
I then used a small converted database and imported all of the date from it
to the newly created database, and the imported data worked apart from a
couple of errors showing On Click problems on buttons and some VBA problems.
After deleting buttons and re-createing them, the new database is now fully
working.

My main database (converted to 2000) is very complex and has multiple forms
(loads of buttons) and VBA functions, and although I imported the data into
a newly created database, (The age converstion now works OK) It will take
for ever sorting out the On click errors buttons and VBA errors.

The main problem is created during converstion to 2000.
Any one know of any fixes for either the Newly created or the converted
databases to overcome this problem.

Regards
Ken