No access path defined for relation.

Deskin, Bob Bob.Deskin@Cognos.COM
Wed, 24 Nov 2004 09:29:19 -0500


This is a multi-part message in MIME format.

------_=_NextPart_001_01C4D231.FC34ECE7
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I suggest logging a call with support. This sounds familiar but I don't
recall the exact circumstances.
=20
Bob

	-----Original Message-----
	From: Maeve Hooper [mailto:mhooper@mhg.co.za]=20
	Sent: November 24, 2004 9:26 AM
	To: Deskin, Bob; powerh-l@lists.sowder.com
	Cc: Paul Howard (E-mail); Mellina Coutouvidis
	Subject: RE: No access path defined for relation.
=09
=09
	Sorry - I should have said we get it in Quick. The code compiles
fine - there is an access statement. So far, it is the same screen but
not all the time ie. we can't reproduce it. The message appears as the
user enters the screen in entry mode - no data has been entered. The
screen is called from a menu, so the user has probably done lots of
other things on other screens before getting this error.  This table is
widely used across the system.
	=20
	We moved to 8.43d from 8.43c.We weren't getting the error before
then, but we did change boxes at the same time so it is possible there
is also a setup issue.?

		-----Original Message-----
		From: Deskin, Bob [mailto:Bob.Deskin@Cognos.COM]
		Sent: Wednesday, November 24, 2004 4:09 PM
		To: Maeve Hooper; powerh-l@lists.sowder.com
		Cc: Paul Howard (E-mail); Mellina Coutouvidis
		Subject: RE: No access path defined for relation.
	=09
	=09
		You don't say where you get the message. Is it QDESIGN?
And did you ever get it before you moved to 8.43D (and from where)?
What's the file type?
		=20
		In QDESIGN, the message means that QDESIGN can't figure
out an access path for the named table. Most files types require that an
access path be established by the time you enter BUILD.
		=20
		When you say intermittent, do you mean within the same
screen or across many screens. If the latter, check those screens and
make sure an access path has been established. It is possible that
things were tightened up in D.
		Bob Deskin             =20
		Senior Product Manager, Application Development Tools,
Cognos Inc.=20
		bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613)
727-1178=20
		3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G
4K9 CANADA=20

			-----Original Message-----
			From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Maeve Hooper
			Sent: November 24, 2004 8:47 AM
			To: powerh-l@lists.sowder.com
			Cc: Paul Howard (E-mail); Mellina Coutouvidis
			Subject: No access path defined for relation.
		=09
		=09


			Hello=20

			Does anybody know anything about this Powerhouse
message. We are getting it intermittently (We have recently upgraded to
Powerhouse 843d). We are running against Sybase 12.5.0.3 and HP-UX 11.11

				 No access path defined for relation.
(STAFF*01)=20

				(Staff is the name of one of our
tables).=20

				Thanks!=20

			Maeve Hooper=20

		=20

		       This message may contain privileged and/or
confidential information.  If you have received this e-mail in error or
are not the intended recipient, you may not use, copy, disseminate or
distribute it; do not open any attachments, delete it immediately from
your system and notify the sender promptly by e-mail that you have done
so.  Thank you.=20


------_=_NextPart_001_01C4D231.FC34ECE7
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:eXclaimer =3D=20
"http://www.exclaimer.co.uk"><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2523" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D380302914-24112004><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
suggest logging a call with support. This sounds familiar but I don't =
recall the=20
exact circumstances.</FONT></SPAN></DIV>
<DIV><SPAN class=3D380302914-24112004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D380302914-24112004><FONT face=3DArial color=3D#0000ff =

size=3D2>Bob</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> =
Maeve Hooper=20
  [mailto:mhooper@mhg.co.za] <BR><B>Sent:</B> November 24, 2004 9:26=20
  AM<BR><B>To:</B> Deskin, Bob; powerh-l@lists.sowder.com<BR><B>Cc:</B> =
Paul=20
  Howard (E-mail); Mellina Coutouvidis<BR><B>Subject:</B> RE: No access =
path=20
  defined for relation.<BR><BR></FONT></DIV>
  <DIV><SPAN class=3D185492114-24112004><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2>Sorry - I should have said we get it in Quick. The code =
compiles fine -=20
  there is an access statement. So far, it is the same screen but not =
all the=20
  time ie. we can't reproduce it. The message appears as the user enters =
the=20
  screen in entry mode - no data has been entered. The screen is called =
from a=20
  menu, so the user has probably done lots of other things on other =
screens=20
  before getting this error.&nbsp; This table is widely used across the=20
  system.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D185492114-24112004><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D185492114-24112004><FONT face=3DArial =
color=3D#0000ff size=3D2>We=20
  moved to 8.43d from 8.43c.We weren't getting the error before then, =
but we did=20
  change boxes at the same time so it is possible there is also a setup=20
  issue.?</FONT></SPAN></DIV>
  <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> Deskin, Bob=20
    [mailto:Bob.Deskin@Cognos.COM]<BR><B>Sent:</B> Wednesday, November =
24, 2004=20
    4:09 PM<BR><B>To:</B> Maeve Hooper; =
powerh-l@lists.sowder.com<BR><B>Cc:</B>=20
    Paul Howard (E-mail); Mellina Coutouvidis<BR><B>Subject:</B> RE: No =
access=20
    path defined for relation.<BR><BR></FONT></DIV>
    <DIV>
    <DIV><SPAN class=3D684400514-24112004><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2>You don't say where you get the message. Is it QDESIGN? And =
did you=20
    ever get it before you moved to 8.43D (and from where)? What's the =
file=20
    type?</FONT></SPAN></DIV>
    <DIV><SPAN class=3D684400514-24112004><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D684400514-24112004><FONT face=3DArial =
color=3D#0000ff size=3D2>In=20
    QDESIGN, the message means that QDESIGN can't figure out an access =
path for=20
    the named table. Most files types require that an access path be =
established=20
    by the time you enter BUILD.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D684400514-24112004><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV><SPAN class=3D684400514-24112004><FONT face=3DArial =
color=3D#0000ff=20
    size=3D2>When you say intermittent, do you mean within the same =
screen or=20
    across many screens. If the latter, check those screens and make =
sure an=20
    access path has been established. It is possible that things were =
tightened=20
    up in D.</FONT></SPAN></DIV>
    <DIV><SPAN class=3D684400514-24112004><!-- Converted from text/rtf =
format -->
    <P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Bob=20
    =
Deskin&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    </FONT></SPAN><BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>Senior Product=20
    Manager, Application Development Tools, Cognos Inc.</FONT></SPAN> =
<BR><SPAN=20
    lang=3Den-us><FONT face=3DArial size=3D2>bob.deskin@cognos.com (613) =
738-1338 ext=20
    7268 FAX: (613) 727-1178</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT =
face=3DArial=20
    size=3D2>3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G =
4K9=20
    CANADA</FONT></SPAN> </P></SPAN></DIV>
    <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
      <DIV></DIV>
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
      face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
      powerh-l-admin@lists.sowder.com =
[mailto:powerh-l-admin@lists.sowder.com]=20
      <B>On Behalf Of </B>Maeve Hooper<BR><B>Sent:</B> November 24, 2004 =
8:47=20
      AM<BR><B>To:</B> powerh-l@lists.sowder.com<BR><B>Cc:</B> Paul =
Howard=20
      (E-mail); Mellina Coutouvidis<BR><B>Subject:</B> No access path =
defined=20
      for=20
      relation.<BR><BR></FONT></DIV><!-- Converted from text/rtf format =
--><BR>
      <P><FONT face=3DArial size=3D2>Hello</FONT> </P>
      <P><FONT face=3DArial size=3D2>Does anybody know anything about =
this=20
      Powerhouse message. We are getting it intermittently (We have =
recently=20
      upgraded to Powerhouse 843d). We are running against Sybase =
12.5.0.3 and=20
      HP-UX 11.11</FONT></P>
      <UL>
        <P><FONT face=3DArial color=3D#000000 size=3D2><I>&nbsp;No =
access path defined=20
        for relation. (STAFF*01)</I></FONT> </P>
        <P><I><FONT face=3DArial color=3D#000000 size=3D2>(Staff is the =
name of one of=20
        our tables).</FONT></I> </P>
        <P><I><FONT face=3DArial color=3D#000000 =
size=3D2>Thanks!</FONT></I> </P></UL>
      <P><FONT face=3DArial size=3D2>Maeve Hooper</FONT> =
</P></BLOCKQUOTE></DIV>
    <DIV>&nbsp;</DIV>
    <DIV>
    <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<FONT face=3DArial =
size=3D2>This=20
    message may contain privileged and/or confidential =
information.&nbsp; If you=20
    have received this e-mail in error or are not the intended =
recipient, you=20
    may not use, copy, disseminate or distribute it; do not open any=20
    attachments, delete it immediately from your system and notify the =
sender=20
    promptly by e-mail that you have done so.&nbsp; Thank you.</FONT>=20
  </P></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C4D231.FC34ECE7--