Re: Type Mismatch Error Fixed when Move ADO reference up - Why?

Thank you, Allen. I'm so glad it's not me!

There are only 2 of us who even write queries and reports (and I am the
only one who writes code), and IT wanted us to upgrade to 2003,
thinking that it would be simple, and he could upgrade to 2003 for new
users. I suspected this wasn't a "workable plan", and you have now
confirmed that for us. THANKS!

Also, I have been using your Change Tracking with tremendous success -
thanks for that, too. It is really easy to install and use. At an
upcoming user group meeting, one of the group's organizers said he'd
explain what all your code was doing as well.

Thanks for all your help! I'd never have made it this far without it.
Sara


Allen Browne wrote:
Each version of Access uses a different binary for the compiled version of
the code. They are backwards compatible (e.g. Access 2003 can read an Access
2002/3 format file compiled into an mde on Access 2002, but not the other
way around.) So, when you have been editing the MDB on 2003, and then open
it in 2000, Access is supposed to silently recompile in the 2000 code, and
everything should run sweetly. In practice that does not happen reliably.

We have found it necessary to explicitly decompile whenever you switch back
to an older version. To decompile, make a backup copy, and enter something
like this at the command prompt while Access is not running. It is all one
line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
Then restart Access (without running any startup code, e.g. hold down the
Shift key), and compact (again holding down Shift.) Then open in the old
version.

It may also help to be explicit about the libaray you want when you declare
references that could be another library, e.g.:
Dim db As DAO.Database
Dim rs As DAO.Recordset
Dim fld As DAO.Field

And the other crucial aspect is to make sure all versions have at least SP8
for JET 4:
http://support.microsoft.com/kb/239114

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"sara" <saraqpost@xxxxxxxxx> wrote in message
news:1156424773.024546.20750@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have an A2K database that has links to 3 of my other databases
(external links) to run some reports. The coding in any of the 4 is
pretty simple.

Recently when we make a new .mde for the "main" database, the first
time we run our reports (all executed from code from a form), we get a
Type Mismatch Error on the line:

Set db = CurrentDb

I go into Tools/References and move MS DAO 3.6 up above my external DB
references and above OLE automation, and make a new mde.
The problem goes away.

The problem is occuring in the MAIN db (not any of the referenced dbs).


The only thing that has changed is that we started using Access 2003 to
do some editing. Of course, we use A2K to make the mde.

Anyone have any thoughts? Aside from the fact that it's annoying, I am
worried something else is wrong and I'm just lucky to have it fixed
with the move of the reference.

Thanks
sara

.

Relevant Pages

  • Re: Type Mismatch Error Fixed when Move ADO reference up - Why?
    ... Dim rs As DAO.Recordset ... to run some reports. ... Recently when we make a new .mde for the "main" database, ... references and above OLE automation, ...
    (comp.databases.ms-access)
  • Re: X error : Major opcode: 151
    ... Here are the reports from a few various programs, ... The error was 'BadRequest (invalid request code or no such operation)'. ... Upgrade xorg in Sid breaks link. ...
    (Debian-User)
  • Re: too many modules
    ... I feel good about not having many empty modules, ... we have enough forms and reports with code ... the parent app has to be the ... Use references to create forms/modules that reside outside the mde ...
    (microsoft.public.access.modulesdaovba)
  • Re: UCase not recognized
    ... I have used Ucase in several reports in an Access 2003 ADP with SQLServer. ... That PC has a missing reference. ... On the Tools menu, click References. ...
    (microsoft.public.access.reports)
  • Re: too many modules
    ... Another thing to consider is that many of your forms and reports might have ... Option Compare Database ... the parent app has to be the ... Use references to create forms/modules that reside outside the mde ...
    (microsoft.public.access.modulesdaovba)