Problem converting Access 97 db to Access 2002

  • Thread starter Thread starter John Smith
  • Start date Start date
J

John Smith

Sorry for the cross-posting, but I'm not quite sure which group is the
appropriate one to post this problem to.


My wife has created a small Access 97 app on Win2000 Pro. She now wants to
move it to Access 2002 on XP Home. She is not an Access guru...this is the
first time she has ever done any programming of any sort, and I have no
specific knowledge of Access (ask me about Oracle or Rdb on OpenVMS)..... be
gentle with me :-)


She has tried to stay away from VBA as much as possible so she's been using
the Wizards for the most part.

Anyway, she got the app to work the way she wanted under Access 97. To move
the app to XP/Access 2002 I copied her .mdb file on to the XP machine and
then she launched the app using Access 2002.

When it first came up we got a standard conversion message asking whether we
wanted to convert to 2002 format or to keep it as 97 format. We elected to
convert to 2002 format. While the conversion took place we got an error
message saying that there was an error in conversion and to look in the
Conversion Error Table for details. Here's what the table had in it:

Object Type Desc
------------ -----
Database Missing or broken VBE reference
to the file IEAWSDC.DLL

Module There were compilation errors during the
conversion or enabling of this database.

(we also tried just keeping it as an Access 97 base on the XP machine, with
the same problem)


So we follow the instructions in the help about opening a module and
clearing the check mark next to the missing item.

What was missing was 'Microsoft Office Template and Media Control 1.0 Type
Library', and it referred to \winnt\Downloaded Program Files\ieawsdc.dll' .
This is clearly references something on the Win2000 machine as the WinXP
install folder is "\Windows", not "\winnt".

So I hunt in the \winnt\Downloaded Program Files folder on the Win2000
machine and see that ieawsdc.dll is 'installed' there. When I click on it to
see its properties I see that it is dependent on ieawsdc.dll* and
ieawsdc.inf*, and that the codebase references
http://office/microsoft.com/templates/ieawsdc.ca

I went to the MS site and look for this goodie but didn't see it (or it's
not obvious). I even did a search on the MS site for 'ieawsdc' and nothing
turns up.

[Aside:] While creating her app, my wife searched around the net for
examples and ideas on how to do some of the programming tasks she wanted to
accomplish and I guess she may have downloaded something from this Microsoft
site and somehow 'installed' it, though she swears that she is not using it
(maybe yes, maybe no).


So now I have a few questions:

1) How can I easily search through all her code to see if she
somehow/somewhere references this ieawsdc.dll in her work? I'm thinking that
if it really isn't used, I ought to be able to remove the references to it
and the migration to XP/Access 2002 should work ok. Again, she's a newbie at
Access and programming and maybe something she inadvertently used references
this...I just don't know for certain.

2) Does anybody have any idea what the heck this .dll does?

3) Seeing as I can't find it on the MS web site, can I copy the .dll it
from the Win2000 machine over to the WinXP machine and somehow 'install' it?
If so, how do I *install* it?

4) Any other ideas on how to resolve this problem and help her get the app
running on Access 2002?

TIA.
 
Sorry, I don't have answers to all of your questions, but try removing the
broken reference and do a compile on the application (it's on the Debug menu
when you've got a code module open). If you don't get any errors, then you
don't need the reference.

--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)



John Smith said:
Sorry for the cross-posting, but I'm not quite sure which group is the
appropriate one to post this problem to.


My wife has created a small Access 97 app on Win2000 Pro. She now wants to
move it to Access 2002 on XP Home. She is not an Access guru...this is the
first time she has ever done any programming of any sort, and I have no
specific knowledge of Access (ask me about Oracle or Rdb on OpenVMS)..... be
gentle with me :-)


She has tried to stay away from VBA as much as possible so she's been using
the Wizards for the most part.

Anyway, she got the app to work the way she wanted under Access 97. To move
the app to XP/Access 2002 I copied her .mdb file on to the XP machine and
then she launched the app using Access 2002.

When it first came up we got a standard conversion message asking whether we
wanted to convert to 2002 format or to keep it as 97 format. We elected to
convert to 2002 format. While the conversion took place we got an error
message saying that there was an error in conversion and to look in the
Conversion Error Table for details. Here's what the table had in it:

Object Type Desc
------------ -----
Database Missing or broken VBE reference
to the file IEAWSDC.DLL

Module There were compilation errors during the
conversion or enabling of this database.

(we also tried just keeping it as an Access 97 base on the XP machine, with
the same problem)


So we follow the instructions in the help about opening a module and
clearing the check mark next to the missing item.

What was missing was 'Microsoft Office Template and Media Control 1.0 Type
Library', and it referred to \winnt\Downloaded Program Files\ieawsdc.dll' ..
This is clearly references something on the Win2000 machine as the WinXP
install folder is "\Windows", not "\winnt".

So I hunt in the \winnt\Downloaded Program Files folder on the Win2000
machine and see that ieawsdc.dll is 'installed' there. When I click on it to
see its properties I see that it is dependent on ieawsdc.dll* and
ieawsdc.inf*, and that the codebase references
http://office/microsoft.com/templates/ieawsdc.ca

I went to the MS site and look for this goodie but didn't see it (or it's
not obvious). I even did a search on the MS site for 'ieawsdc' and nothing
turns up.

[Aside:] While creating her app, my wife searched around the net for
examples and ideas on how to do some of the programming tasks she wanted to
accomplish and I guess she may have downloaded something from this Microsoft
site and somehow 'installed' it, though she swears that she is not using it
(maybe yes, maybe no).


So now I have a few questions:

1) How can I easily search through all her code to see if she
somehow/somewhere references this ieawsdc.dll in her work? I'm thinking that
if it really isn't used, I ought to be able to remove the references to it
and the migration to XP/Access 2002 should work ok. Again, she's a newbie at
Access and programming and maybe something she inadvertently used references
this...I just don't know for certain.

2) Does anybody have any idea what the heck this .dll does?

3) Seeing as I can't find it on the MS web site, can I copy the .dll it
from the Win2000 machine over to the WinXP machine and somehow 'install' it?
If so, how do I *install* it?

4) Any other ideas on how to resolve this problem and help her get the app
running on Access 2002?

TIA.
Click to expand...
 
Hi John,

Although IEAWSDC.DLL sounds like it might be related to Internet Explorer, I found that it
is not included in the DLL Help Database at Microsoft:
http://support.microsoft.com/default.aspx?scid=/servicedesks/fileversion/dllinfo.asp

Who knows where this strange .DLL file might have come from! I don't think I'd worry
about it. Try removing this checked reference from the Tools > References dialog box,
which is available within the VBE editor. Then try doing a Debug > Compile operation.
Does the code compile okay? If so, then your problems are probably over.

You can use the Find toolbar button (or Edit > Find) from the menu in the VBE editor to
search all code for this .DLL file.

Tom
________________________________________


Sorry for the cross-posting, but I'm not quite sure which group is the
appropriate one to post this problem to.


My wife has created a small Access 97 app on Win2000 Pro. She now wants to
move it to Access 2002 on XP Home. She is not an Access guru...this is the
first time she has ever done any programming of any sort, and I have no
specific knowledge of Access (ask me about Oracle or Rdb on OpenVMS)..... be
gentle with me :-)


She has tried to stay away from VBA as much as possible so she's been using
the Wizards for the most part.

Anyway, she got the app to work the way she wanted under Access 97. To move
the app to XP/Access 2002 I copied her .mdb file on to the XP machine and
then she launched the app using Access 2002.

When it first came up we got a standard conversion message asking whether we
wanted to convert to 2002 format or to keep it as 97 format. We elected to
convert to 2002 format. While the conversion took place we got an error
message saying that there was an error in conversion and to look in the
Conversion Error Table for details. Here's what the table had in it:

Object Type Desc
------------ -----
Database Missing or broken VBE reference
to the file IEAWSDC.DLL

Module There were compilation errors during the
conversion or enabling of this database.

(we also tried just keeping it as an Access 97 base on the XP machine, with
the same problem)


So we follow the instructions in the help about opening a module and
clearing the check mark next to the missing item.

What was missing was 'Microsoft Office Template and Media Control 1.0 Type
Library', and it referred to \winnt\Downloaded Program Files\ieawsdc.dll' .
This is clearly references something on the Win2000 machine as the WinXP
install folder is "\Windows", not "\winnt".

So I hunt in the \winnt\Downloaded Program Files folder on the Win2000
machine and see that ieawsdc.dll is 'installed' there. When I click on it to
see its properties I see that it is dependent on ieawsdc.dll* and
ieawsdc.inf*, and that the codebase references
http://office/microsoft.com/templates/ieawsdc.ca

I went to the MS site and look for this goodie but didn't see it (or it's
not obvious). I even did a search on the MS site for 'ieawsdc' and nothing
turns up.

[Aside:] While creating her app, my wife searched around the net for
examples and ideas on how to do some of the programming tasks she wanted to
accomplish and I guess she may have downloaded something from this Microsoft
site and somehow 'installed' it, though she swears that she is not using it
(maybe yes, maybe no).


So now I have a few questions:

1) How can I easily search through all her code to see if she
somehow/somewhere references this ieawsdc.dll in her work? I'm thinking that
if it really isn't used, I ought to be able to remove the references to it
and the migration to XP/Access 2002 should work ok. Again, she's a newbie at
Access and programming and maybe something she inadvertently used references
this...I just don't know for certain.

2) Does anybody have any idea what the heck this .dll does?

3) Seeing as I can't find it on the MS web site, can I copy the .dll it
from the Win2000 machine over to the WinXP machine and somehow 'install' it?
If so, how do I *install* it?

4) Any other ideas on how to resolve this problem and help her get the app
running on Access 2002?

TIA.
 
Just to add to John's and Dougles good comments:

You want to test/compile the code on the a97 machine BEFORE you try and
convert. Likely, there is some code that was sitting there that does not
compile.

So, while looking at code, do a debug->compile and save all modules in a97.

I would also just simply un-check/remove that reference, as likely you don't
need it.
 
Thanks to all who responded. Looks like your suggestions did the trick.

Now all she has to do is figure out how she can secure the app properly for
users while still giving herself full developer rights and capabilities. But
that's another question and another post to come later....
 
John,

Have her download a copy of the Access Security FAQ. A link to this paper is available on
this site:

http://www.mvps.org/access/resources/techpapers.htm

Advise her to read this paper thoroughly several times, and to practice on a copy of her
database. Finally, advise her that implementing Access security simply raises the bar
against unauthorized access. You will never achieve the level of security that is
available with SQL Server.....

__________________________________________


Thanks to all who responded. Looks like your suggestions did the trick.

Now all she has to do is figure out how she can secure the app properly for
users while still giving herself full developer rights and capabilities. But
that's another question and another post to come later....
 
Back
Top