RE: Access 2000

From: TAL1 (TAL1_at_discussions.microsoft.com)
Date: 01/03/05 

Date: Mon, 3 Jan 2005 12:35:04 -0800

Thanks Steve. It ended up being that there is a difference between the
acceptable file names between Windows NT and 2000. NT either does not
support file names that have spaces in them or possibly the length. I did
not test to see which it was. For some reason this only effected .mde files
possibly because of the links.

Thanks for your help!!

"Stephen Knapp" wrote:

> TAL:
>
> Is isn't so much an issue of Windows 2000 versus NT but, rather, the
> setup differences between your users. The first thing I'd look at is the
> version of MDAC that is running on the various machines. Microsoft Data
> Access Components is a gaggle of software (mostly DLLs) that are used
> throughout Windows, including Access. On the Microsoft web site, search for
> "MDAC" and look for the version analysis software. It downloads quickly and
> when you run it, it checks all of the MDAC modules and determines which
> version of MDAC they apply to. Start by checking one of the "good" machines,
> then one of the workstations having problems. You might have to upgrade the
> MDAC on the NT workstations. P.s. this isn't fun. I've been there - done
> that. Note that MDAC versions 2.5 and higher DO NOT have the Jet engine
> included (MS separate it out at this point), so you'll have to make sure that
> the Jet is up to date, as well.
>
> (When you are finished with this correspondence thread, click the YES or NO
> button on your original posting to close the discussion. Or, go to your
> profile and close the thread from there – Steve.)
>
> "TAL1" wrote:
>
> > I have a database that I have converted to be an MDE file. I have
> > distributed it on a network to multiple users. The other users have recently
> > been upgraded from Access 97. When accessing the database about half of the
> > users get an error message Microsoft Jet database cannot find the input table
> > or query database table, make sure it exists and that the name is spelled
> > correctly". We have reinstalled the Jet engine and the error was not
> > resolved. Since the database works fine on about half of the systems I am
> > leaning toward it having something to do with Access maybe a dll file. Can
> > you help?