Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

migrating from access 2000 to access 2003

Discussion in 'Information Technology' started by Ron, Jul 28, 2006.

  1. Ron

    Ron
    Expand Collapse
    Guest

    HELP ... everything I read says that an Access 2000 db should run with no
    problems under 2003. However, this is not my case. The db under 2000 has run
    for years and now with 2003 I get errors that seem to be related to
    "built-in" functions that 2003 says it can't find.

    I have tried this db under Office XP and it functiions without problems.

    I do NOT have data Access Pages which is the only thing I find as needing
    converting.

    I need to transfer this project to a person that has 2003 and we need it
    running soon.

    Thanks for any and all help anyone can provide.
     
  2. Loading...


  3. Douglas J Steele

    Douglas J Steele
    Expand Collapse
    Guest

    Likely a problem with the References collection. This is common if there are
    different versions of software between the machine where the application was
    developed and those on which it's going to be run.

    On the machine(s) where it's not working, open any code module, then 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, under the Debug menu), 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)


    --
    Doug Steele, Microsoft Access MVP
    http://I.Am/DougSteele
    (no e-mails, please!)


    "Ron" <Ron@discussions.microsoft.com> wrote in message
    news:82835A0C-26F5-4A72-8CD4-2DAFAAB6B384@microsoft.com...
    > HELP ... everything I read says that an Access 2000 db should run with no
    > problems under 2003. However, this is not my case. The db under 2000 has

    run
    > for years and now with 2003 I get errors that seem to be related to
    > "built-in" functions that 2003 says it can't find.
    >
    > I have tried this db under Office XP and it functiions without problems.
    >
    > I do NOT have data Access Pages which is the only thing I find as needing
    > converting.
    >
    > I need to transfer this project to a person that has 2003 and we need it
    > running soon.
    >
    > Thanks for any and all help anyone can provide.
     
  4. Ron

    Ron
    Expand Collapse
    Guest

    Thanks ... Will give it a try. Sure hope this does it.

    "Ron" wrote:

    > HELP ... everything I read says that an Access 2000 db should run with no
    > problems under 2003. However, this is not my case. The db under 2000 has run
    > for years and now with 2003 I get errors that seem to be related to
    > "built-in" functions that 2003 says it can't find.
    >
    > I have tried this db under Office XP and it functiions without problems.
    >
    > I do NOT have data Access Pages which is the only thing I find as needing
    > converting.
    >
    > I need to transfer this project to a person that has 2003 and we need it
    > running soon.
    >
    > Thanks for any and all help anyone can provide.
     
  5. Ron

    Ron
    Expand Collapse
    Guest

    Just trying to check this out and it appears this relates to coded modules.
    My errors come from within a report or macros and relate to functions such as
    IIF and LEN and MID. References only seem to be available to me when I open a
    basic module.


    "Ron" wrote:

    > Thanks ... Will give it a try. Sure hope this does it.
    >
    > "Ron" wrote:
    >
    > > HELP ... everything I read says that an Access 2000 db should run with no
    > > problems under 2003. However, this is not my case. The db under 2000 has run
    > > for years and now with 2003 I get errors that seem to be related to
    > > "built-in" functions that 2003 says it can't find.
    > >
    > > I have tried this db under Office XP and it functiions without problems.
    > >
    > > I do NOT have data Access Pages which is the only thing I find as needing
    > > converting.
    > >
    > > I need to transfer this project to a person that has 2003 and we need it
    > > running soon.
    > >
    > > Thanks for any and all help anyone can provide.
     
  6. dbahooker@hotmail.com

    dbahooker@hotmail.com
    Expand Collapse
    Guest

    I would guess that you just need to go tools, macros security = low or
    something

    -Aaron



    Ron wrote:
    > HELP ... everything I read says that an Access 2000 db should run with no
    > problems under 2003. However, this is not my case. The db under 2000 has run
    > for years and now with 2003 I get errors that seem to be related to
    > "built-in" functions that 2003 says it can't find.
    >
    > I have tried this db under Office XP and it functiions without problems.
    >
    > I do NOT have data Access Pages which is the only thing I find as needing
    > converting.
    >
    > I need to transfer this project to a person that has 2003 and we need it
    > running soon.
    >
    > Thanks for any and all help anyone can provide.
     
  7. Ron

    Ron
    Expand Collapse
    Guest

    Have found and corrected the problem. The problem was with a missing file,
    MSOWC.DLL, in the Access 2003 Office11 folder. Copied the file into that
    folder and everything works fine.

    If you need this file, you can download a copy from

    http://www.dlldump.com/download-dll-files.php/dllfiles/M/MSOWC.DLL/download.html

    Hope this help save others all the time I spent trying to solve this.


    "Ron" wrote:

    > Just trying to check this out and it appears this relates to coded modules.
    > My errors come from within a report or macros and relate to functions such as
    > IIF and LEN and MID. References only seem to be available to me when I open a
    > basic module.
    >
    >
    > "Ron" wrote:
    >
    > > Thanks ... Will give it a try. Sure hope this does it.
    > >
    > > "Ron" wrote:
    > >
    > > > HELP ... everything I read says that an Access 2000 db should run with no
    > > > problems under 2003. However, this is not my case. The db under 2000 has run
    > > > for years and now with 2003 I get errors that seem to be related to
    > > > "built-in" functions that 2003 says it can't find.
    > > >
    > > > I have tried this db under Office XP and it functiions without problems.
    > > >
    > > > I do NOT have data Access Pages which is the only thing I find as needing
    > > > converting.
    > > >
    > > > I need to transfer this project to a person that has 2003 and we need it
    > > > running soon.
    > > >
    > > > Thanks for any and all help anyone can provide.
     
  8. dbahooker@hotmail.com

    dbahooker@hotmail.com
    Expand Collapse
    Guest

    dude downloading from a 3rd party site liek that is risky.

    Make sure oyu download the latest version; the full installer; the
    latest version-- should be included with the Office 2003 Service Pack
    install.

    HTH i fight OWC all the time.

    -Aaron


    Ron wrote:
    > Have found and corrected the problem. The problem was with a missing file,
    > MSOWC.DLL, in the Access 2003 Office11 folder. Copied the file into that
    > folder and everything works fine.
    >
    > If you need this file, you can download a copy from
    >
    > http://www.dlldump.com/download-dll-files.php/dllfiles/M/MSOWC.DLL/download.html
    >
    > Hope this help save others all the time I spent trying to solve this.
    >
    >
    > "Ron" wrote:
    >
    > > Just trying to check this out and it appears this relates to coded modules.
    > > My errors come from within a report or macros and relate to functions such as
    > > IIF and LEN and MID. References only seem to be available to me when I open a
    > > basic module.
    > >
    > >
    > > "Ron" wrote:
    > >
    > > > Thanks ... Will give it a try. Sure hope this does it.
    > > >
    > > > "Ron" wrote:
    > > >
    > > > > HELP ... everything I read says that an Access 2000 db should run with no
    > > > > problems under 2003. However, this is not my case. The db under 2000 has run
    > > > > for years and now with 2003 I get errors that seem to be related to
    > > > > "built-in" functions that 2003 says it can't find.
    > > > >
    > > > > I have tried this db under Office XP and it functiions without problems.
    > > > >
    > > > > I do NOT have data Access Pages which is the only thing I find as needing
    > > > > converting.
    > > > >
    > > > > I need to transfer this project to a person that has 2003 and we need it
    > > > > running soon.
    > > > >
    > > > > Thanks for any and all help anyone can provide.
     

Share This Page