Upgrade issues from 97 to 2003 - references? DATE LEFT and FORMAT give compile errors

[arthur-e]

A new Machine was set up by our IS department -
it came with Office Pro 2003.
Access97, Word97 and Excel 97 were added.

I'm trying to update an Access 97database to 2003 but get weird
compiling errors -
Date, Format and Left give errors.

I've registered the missing (or those ocx's) that were indicated as
missing- iincluding - mscomct2.ocx - and the date picker showed up but
simple things like DATE FORMAT and LEFT give compile errors

- any ideas? -

I've looked at Allen Browne's amazing site - his "Solving Problems
with Library References" members.iinet.net.au/~allenbrowne/ser-38.html
but either I couldn't figure out the right thing to do - or the
solution is not here.

Could there be different versions of dao360.dll that conflict??

Any ideas? help?

[Allen Browne]

Arthur, how far have you got?

I take it that the conversion process succeeded (i.e. it did create an A2003
mdb file), but the new file gives errors in the most basic code?

You have gone to References on the Tools menu (from a code window), and
re-registered the references, so none are now showing up as "MISSING"?

Which references do you have selected?

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"arthur-e" <ar*****@ix.netcom.com> wrote in message
news:ni********************************@4ax.com...

A new Machine was set up by our IS department -
it came with Office Pro 2003.
Access97, Word97 and Excel 97 were added.

I'm trying to update an Access 97database to 2003 but get weird
compiling errors -
Date, Format and Left give errors.

I've registered the missing (or those ocx's) that were indicated as
missing- iincluding - mscomct2.ocx - and the date picker showed up but
simple things like DATE FORMAT and LEFT give compile errors

- any ideas? -

I've looked at Allen Browne's amazing site - his "Solving Problems
with Library References" members.iinet.net.au/~allenbrowne/ser-38.html
but either I couldn't figure out the right thing to do - or the
solution is not here.

Could there be different versions of dao360.dll that conflict??

Any ideas? help?

[Arthur E]

Allen - Thanks so much.
the I reread some of the info on your site. I unchecked a missing link
in the references to an Access 97 database which is linked to the one I
was updating. The strange reference errors dissapeared. I had been
leery of unchecking the link but did, and I "think" I've got much of the
trouble fixed.

I still have problems when running another Access97 database that opens
a Word document because that word2000 tries to open another instance of
Access - but that instance has no data loaded in the form so the link
fails.
1. If I open Word97 before running the code to do the mail merge - the
merge usually works.

Do you know how to make the Access 97 database use Word97 and NOT try to
load another instance of Access?? - if so that would be a great help
while i'm moving the office to Access 2003.
This is a small office (five machines) for the biomed research
management at a hospital in NYC. - THaNKS in advance.

New York Photos at www.arthure212.bravepages.com

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Allen Browne]

From memory, Word 97 opened another instance of Access if you were using a
customized title bar, i.e. if you have anything in:
Tools | Startup | Application Title

Late binding can also get you out of a spot where an application needs to
work across multiple versions of Access. This article should get you
started:
http://support.microsoft.com/default...b;en-us;242375

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Arthur E" <ar*****@ix.netcom.com> wrote in message
news:42**********@127.0.0.1...

Allen - Thanks so much.
the I reread some of the info on your site. I unchecked a missing link
in the references to an Access 97 database which is linked to the one I
was updating. The strange reference errors dissapeared. I had been
leery of unchecking the link but did, and I "think" I've got much of the
trouble fixed.

I still have problems when running another Access97 database that opens
a Word document because that word2000 tries to open another instance of
Access - but that instance has no data loaded in the form so the link
fails.
1. If I open Word97 before running the code to do the mail merge - the
merge usually works.

Do you know how to make the Access 97 database use Word97 and NOT try to
load another instance of Access?? - if so that would be a great help
while i'm moving the office to Access 2003.
This is a small office (five machines) for the biomed research
management at a hospital in NYC. - THaNKS in advance.