Weird Type Mismatch Error

[PeaceManGroove]

It's a long story, but our application needs to run in Access 97.
All of the computers in our organisation also run Access 2003. . .

C++ code launches our Access reports via a VB 6.0 program.

I added code to the VB6 to specify Access.Application.8 object.
This was meant to ensure that our reports open in Access 97 and not
Access 2003.

It got though testing and works for the most part, but here comes the
weird stuff . . . .

When Access 2003 has not been deployed (ie. run for the first time)
users are getting Error 13: Type Mismatch ??

It seems that Access.Application.8 is only valid if there is another
version of Access registered on a machine (and not just Access 97).

This is really painful because the SOE states that Access 2003 is an
all machines, the problem is it isn't necessarily "deployed" /
registered properly !?!?

Does anyone have words of wisdom that may help ??

Regards
PeaceMan

[Tom van Stiphout]

On 17 Apr 2007 20:28:05 -0700, PeaceManGroove
<gr*********@hotmail.comwrote:

I used to think as well that:
CreateObject("Access.Application.8")
creates an A97 object. Not necessarily so. There is a MSFT article
about this (if I recall correctly it's more general in nature,
addressing any com component e.g. adodb.connection.2.5 has the same
problem). I'm sure you can find it.

-Tom.

>It's a long story, but our application needs to run in Access 97.
All of the computers in our organisation also run Access 2003. . .

C++ code launches our Access reports via a VB 6.0 program.

I added code to the VB6 to specify Access.Application.8 object.
This was meant to ensure that our reports open in Access 97 and not
Access 2003.

It got though testing and works for the most part, but here comes the
weird stuff . . . .

When Access 2003 has not been deployed (ie. run for the first time)
users are getting Error 13: Type Mismatch ??

It seems that Access.Application.8 is only valid if there is another
version of Access registered on a machine (and not just Access 97).

This is really painful because the SOE states that Access 2003 is an
all machines, the problem is it isn't necessarily "deployed" /
registered properly !?!?

Does anyone have words of wisdom that may help ??

Regards
PeaceMan