Connecting Tech Pros Worldwide Forums | Help | Site Map

Type Mismatch error in MDE file

jodyblau
Guest
 
Posts: n/a
#1: Apr 10 '06
I am getting a type mismatch message under strange circumstances.
Here's whats going on:

1. I have split the database into a front end and a back end.

2. I have compiled the project.

3. I update the linked tables and then make an mde file.

4. When I use the mdb file, everything seems to work fine.

5. When I use the MDE file, I get a type mismatch error.

6. If I copy the entire database and take it home and follow the same
steps as outlined above, I don't get the error.

I don't understand what factor changes which causes the error. I know
which section of code is producing the typemismatch error, but I don't
know why it works fine as an MDB file but not as an MDE file.

Does anyone know what might be going on here?

Thanks,

Jody


MGFoster
Guest
 
Posts: n/a
#2: Apr 11 '06

re: Type Mismatch error in MDE file


jodyblau wrote:[color=blue]
> I am getting a type mismatch message under strange circumstances.
> Here's whats going on:
>
> 1. I have split the database into a front end and a back end.
>
> 2. I have compiled the project.
>
> 3. I update the linked tables and then make an mde file.
>
> 4. When I use the mdb file, everything seems to work fine.
>
> 5. When I use the MDE file, I get a type mismatch error.
>
> 6. If I copy the entire database and take it home and follow the same
> steps as outlined above, I don't get the error.
>
> I don't understand what factor changes which causes the error. I know
> which section of code is producing the typemismatch error, but I don't
> know why it works fine as an MDB file but not as an MDE file.
>
> Does anyone know what might be going on here?[/color]

My guess: A Reference is missing.

Open a VBA module: menu Debug > Compile <project name>. You may get a
"Unknown user-defined .... " error. It may be because you don't have a
reference for that object type. To correct: menu Tools > Reference -
check the object library that holds the erroring object. Usually, in
Access 2000 and above, it is the DAO object library (if you're using DAO
instead of/or with ADO).

Open the References list anyway & check for a checked MISSING item.
Uncheck the Missing item.
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)
Closed Thread