Re: Run-time error '13': Type Mismatch

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hello Chad,

I certainly see cases where the behavior is different between the form and
the report, but for each case this was resolved by applying the sample code
from KB 285820. So I think the best option is to try to use the sample
code directly from the KB to see if this will work for you.

Aside from this, I think the best thing will be to work with someone that
can help debug your actual code with you. Perhaps working with CSS
directly they can better assist in the debugging.

Based on my experience, a problem as complex as this may take extensive
time to narrow down. If the issue is urgent, you may want to work with
Microsoft Customer Service and Support (CSS) for a faster resolution. Once
you open a Support incident with Microsoft CSS, a dedicated Support
Professional can work with you in a more efficient manner.

Please be advised that contacting phone support will be a charged call.

To obtain the phone numbers for a specific technology request please take a
look at the web site listed below.
<http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS>

If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.

Have a great weekend!

Sincerely,

Dana Brash [MSFT]

======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================


--------------------
From: "CEV" <chadv@xxxxxxxxxxxxxx>
References: <esH0ATceGHA.4720@xxxxxxxxxxxxxxxxxxxx>
<#03fA6deGHA.2416@xxxxxxxxxxxxxxxxxxxx>
<OiNO9BfeGHA.1812@xxxxxxxxxxxxxxxxxxxx>
<9SGDeXieGHA.4672@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Run-time error '13': Type Mismatch
Date: Thu, 18 May 2006 13:19:18 -0500
Lines: 110
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-RFC2646: Format=Flowed; Original
Message-ID: <#UmiWeqeGHA.4828@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.access.reports
NNTP-Posting-Host: advancecpe.brookings.net 66.17.96.235
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.access.reports:189060
X-Tomcat-NG: microsoft.public.access.reports

Everything seems to be setup correctly. The thing that gets me is that
when
I am in the main form I will scroll through each person's record. As I
scroll through them, the picture changes to the correct one. Then when I
click the report button to open the report, they all open up except for
about 12 out of over 100. Any other ideals?

Thanks,

Chad

""Dana Brash [MSFT]"" <danabras@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:9SGDeXieGHA.4672@xxxxxxxxxxxxxxxxxxxxxxxx
Hello,

My understanding of this issue is that you may receive the error when the
system has problems resolving the Me![ImagePath] portion. You may want
to
confirm via watch window what the value of ImagePath is when debugging to
confirm that this information is pointing correctly to an existing image.

You may want to check your steps against the below article:

How to display images from a folder in a form, a report, or a data access
page
http://support.microsoft.com/?id=285820

Hope this helps!

Best regards,
Dana

Dana Brash [MSFT]

======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
======================================================
--------------------
From: "CEV" <chadv@xxxxxxxxxxxxxx>
References: <esH0ATceGHA.4720@xxxxxxxxxxxxxxxxxxxx>
<#03fA6deGHA.2416@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: Run-time error '13': Type Mismatch
Date: Wed, 17 May 2006 15:28:38 -0500
Lines: 42
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-RFC2646: Format=Flowed; Response
Message-ID: <OiNO9BfeGHA.1812@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.access.reports
NNTP-Posting-Host: advancecpe.brookings.net 66.17.96.235
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.access.reports:189003
X-Tomcat-NG: microsoft.public.access.reports

Thank You for the response. I did already check that because I was
thinking
the same thing. I also have already created a generic image for those
that
do not have one. I also have there picture showing on the main form and
it
shows up fine. It is when I click the button to open the report when I
get
the error. If there is anything else I should check or if anyone else has
an
ideal, please let me know. This is a report that periodically needs to be
printed as it changes.

Thank You,

CEV

"Duncan Bachen" <dbachen@olehansen_dot_com> wrote in message
news:%2303fA6deGHA.2416@xxxxxxxxxxxxxxxxxxxxxxx
CEV wrote:
Hi, I have created a report that contains info on each person we
serve.
The report has info for only the person selected. In this report there
is
also a picture of the person. The path to the picture is stored in a
field in a table. I can open this report for most people, but on some
I
am getting the above error. When I click on Debug the highlighted line
is: Me![ImageFrame].Picture = Me![ImagePath]. I do not understand why
this is only hapenning for certain records but not others. Someone
PLEASE
guide me in the right direction to resolve this.

My guess is that for those people who it doesn't work for, the path is
either missing, or incorrectly formatted.

That line of text is telling the picture box to load the picture
located
at [ImagePath]. ImagePath needs to be a valid path/filename.

You might consider having a generic picture or something to assign as
the
default value for ImagePath for those folks without a picture.

Compare the record of one person who doesn't work with one that does,
and
you'll likely find the source of your troubles there.

--
-D
Duncan Bachen
Director of I.T., Ole Hansen and Sons, Inc.








.

Quantcast