Recently I have begun experiencing a pretty significant glitch in MS ACCESS 2002 that is causing me a major headache. When attempting to do a simple import of any type of file (.txt,.xls,.dbf etc.) I receive a quick message box that states "Type Mismatch". When I click "OK" it takes me to a pseudo import specification wizard that has a form name of 'mx_FrmMain:Form'.

The wizard is blank and when you click NEXT you get the message:

'The expression you entered refers to an object that is closed or doesn't exist.'

Very bizzare. The really crazy thing is that it is fickle. Some days I can import without issue. Also I have modules d that using vba import .txt files that when fired off have no issue. Yet recently more and more, I am running into this problem and it's preventing myself and other members of my group to not be able to import.

NOTE:

I found only this answer on GOOGLE and the solution did not work. Has anyone else experienced this? Can you help? Thanks a ton...

http://www.mcse.ms/archive148-2004-4-542163.html

Some questions to clarify the situation:

1. When you say "Fickle" - OK, it sometimes works and sometimes doesn't. But is this fickleness machine-dependent? I.e. always on one workstation but never on another?

2. Is anyone doing anything like auto-patching your system on a regular basis?

3. Is this Windows XP and you have Windows File Protection turned on (so that an installed file could get replaced despite its validity)?

4. Are you using only signed .DLL and driver files? (This could be a site policy thing and you might not know the answer, but ask your site manager.)

5. Have you recently done a virus scan on the machines exhibiting this odd behavior?

I admit I'm fishing, trying to better quantify your problem.

1. When you say "Fickle" - OK, it sometimes works and sometimes doesn't. But is this fickleness machine-dependent? I.e. always on one workstation but never on another?

- It's on more than one laptop within our group. I have a desktop in my office as well I use for running various jobs and reports from an old mainframe system that was my old box before my laptop and that imports just fine. We got our new laptops up and running in May or so for my group.

2. Is anyone doing anything like auto-patching your system on a regular basis?

- Yes. Our LAN admin pushes updates to our machines daily or as needed. One concern was that they were scared of SPYWARE so they disabled ACTIVEX components in IE and I've seen other items fail on me related to this but couldn't find the correlation.

3. Is this Windows XP and you have Windows File Protection turned on (so that an installed file could get replaced despite its validity)?

* Windows XP - Yes. Whatever the secure setting is - is probably what is occurring - I'm not sure whether Windows File Protection is turned on.

4. Are you using only signed .DLL and driver files? (This could be a site policy thing and you might not know the answer, but ask your site manager.)

* Don't know. I can doubel check if you think it's applicable.

5. Have you recently done a virus scan on the machines exhibiting this odd behavior?

* Yes. All clean.

From your description and follow-up, I'm torn.

First, ActiveX probably cannot be disabled when you intend to run a Wizard because many of them are based on ActiveX (Automation).

Second, if it is machine specific, two sub-possibilities come to mind.

2a. It is a references issue 'cause references are machine specific. If you update a reference but then auto-patch or some other thing comes along to undo your reference registration, that could be whacking you.

2b. It could be an installation problem if Office was not installed uniformly on all machines. Wizards are installed in the Custom installation in which you get to put a checkmark next to the wizards you want. The default install just chooses a smattering of the more popular wizards.

If it comes and goes on a single machine, one day working perfectly and the next falling down on its chops, look to your site manager's event logs to see if a patch or something else was downloaded to that specific machine between the two cases.

As to Windows File Protection, it is a relatively new thing, XP and 2K had it, that won't let you update the .EXE and some other file types in the \system32 folder. There is a cache in another folder that holds copies of the old files. Get involved with your domain or site administrator or your security folks to find out if this feature is turned on (or perhaps turned on sometimes and not at other times.)

Hi,
I have the same problem, except it is not intermittant, just constant.

I un-installed and re-installed office. Did a regsvr32 on every ms*40.dll I could find. Removed the Acc MDE files. Nothing works. I cannot import text, csv, xls or anything. Running Office for XP with FP.

Help!!

Problem fixed. Did this (registered dao360.dll) :

See MS KB KB296205

(http://support.microsoft.com/kb/q296205/)