Access 2000 to 2003 conversion missing reference and freezing errors

[NEWSGROUPS]

I am in the midst of trying to convert about 25 Access 2000 to Access 2003.
The new environment consists of Office/Access 2003 and Outlook 2003. When
converting the back ends I have no problems. When converting the front ends
I get the following issues and error. If I try to import all the objects
into a blank Access 2003 shell I get a missing reference error for Outlook
2000, Excel 2000, and Word 2000 or after importing all the objects Access
2003 just freezes with the Importing Objects box open. If I open the Access
2000 database in Access 2003 and try to convert I get the missing reference
error for Outlook 2000, Excel 2000, and Word 2000 and it won't convert. I
found that I have to open all the databases in Access 2000 and remove the
Outlook 2000, Excel 2000, and Word 2000 references, convert, and then add
the references to Outlook 2003, Excel 2003, and Word 2003.

Everything I read in these groups say that I should be able to simply import
all my objects into a blank Access 2003 shell or open and convert. Any idea
why I am experiencing these issues. Is there an easier way to go about this.
Any help would be welcome.

Regards,
Markco

[Rick Brandt]

Most apps convert fine becuse they don't have references set to Outlook, Excel,
and Word. Do you really need those? You would be better off using late binding
and eliminating those external references.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[Tony Toews [MVP]]

"NEWSGROUPS" <here...@yahoo.com> wrote:

>Everything I read in these groups say that I should be able to simply import
>all my objects into a blank Access 2003 shell or open and convert. Any idea
>why I am experiencing these issues. Is there an easier way to go about this.
>Any help would be welcome.

Rick is correct. Late binding is the anser.

Late binding means you can safely remove the reference and only have an error when
the app executes lines of code in question. Rather than erroring out while starting
up the app and not allowing the users in the app at all. Or when hitting a mid, left
or trim function call.

You'll want to install the reference if you are programming or debugging and want to
use the object intellisense while in the VBA editor. Then,. once your app is
running smoothly, remove the reference and setup the late binding statements.

Sample code:
' Declare an object variable to hold the object
' reference. Dim as Object causes late binding.
Dim objWordDoc As Object
Set objWordDoc = CreateObject(" Word.Document")

For more information including additional text and some detailed links see the "Late
Binding in Microsoft Access" page at http://www.granite.ab.ca/access/latebinding.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

[NEWSGROUPS]

Thank you Tony and Rick,

Unfortunately the code is already written and would take to long to change
to late binding. I only have 5 days left to get all my databases converted
and the code within is very complex. I guess I will just remove the
references for now, convert and re-added. I will add the late binding code
at a later time. But I don't understand why after removing the references
and importing the objects into a blank 2003 shell, the app freezes up with
the importing objects dialog box still open.

Markco1

"Tony Toews [MVP]" <tto...@telusplanet.net> wrote in message
news:qrv5l3hf1n05gksvq...@4ax.com...

[Tony Toews [MVP]]

"NEWSGROUPS" <here...@yahoo.com> wrote:

>Unfortunately the code is already written and would take to long to change
>to late binding. I only have 5 days left to get all my databases converted
>and the code within is very complex.

I would have setup this code to only be a few subroutines so it's very easy to deal
with and find. In which case this would only be a few or ten minutes to convert
each subroutine.

>But I don't understand why after removing the references
>and importing the objects into a blank 2003 shell, the app freezes up with
>the importing objects dialog box still open.

That shouldn't be happening. And you didn't mention that on your original posting.
This gets more complicated

But even then importing object by object shouldn't be necessary. In A2003 open the
database >> Tools >> Database Utilities >> Convert Database >> To Access 2003 or 2003
format. Then remove the old references and add the new references.

[NEWSGROUPS]

Tony,
Thank you once again for your help. My department is just 2 people with a
very large work load. That being said our goal is to get this code changed
as soon as possible but it will not be possible before the scheduled
completion date for migration.

Best Regards,
Markco

"Tony Toews [MVP]" <tto...@telusplanet.net> wrote in message

news:bk27l3d7l9io992el...@4ax.com...