Pls Help - no clues as to what field

I am running a report that is using a stored proc that has been changed. I
made the changes that I am aware of however there seems to be a field
somewhere in an expression that causes this error ... I cannot figure out how
to locate the field!
It doesnt tell me what expression or what field. The error occurs in report
preview and the text is this:
An error occurred during local report processing.
an unexpected error occurred in the report processing.
the expression referenced a non-existing field in the fields collection.Double check your SQL. If you have something that you have wrapped with a
function (ie. LTRIM(tbl.Field), this will not have a fields name. You
would need to do: LTRIM(tbl.Field) as FieldName
Hope that helps
"MJT" <MJT@.discussions.microsoft.com> wrote in message
news:E98971F5-7FB1-47E9-BDCA-8EE206328488@.microsoft.com...
>I am running a report that is using a stored proc that has been changed. I
> made the changes that I am aware of however there seems to be a field
> somewhere in an expression that causes this error ... I cannot figure out
> how
> to locate the field!
> It doesnt tell me what expression or what field. The error occurs in
> report
> preview and the text is this:
> An error occurred during local report processing.
> an unexpected error occurred in the report processing.
> the expression referenced a non-existing field in the fields collection.
>|||are you saying that I should check the stored procedure? I am not using sql.
I have verified that all the fields are coming back from the stored
procedure and exist in the fields collection so this is very strange.
"Chris" wrote:
> Double check your SQL. If you have something that you have wrapped with a
> function (ie. LTRIM(tbl.Field), this will not have a fields name. You
> would need to do: LTRIM(tbl.Field) as FieldName
> Hope that helps
> "MJT" <MJT@.discussions.microsoft.com> wrote in message
> news:E98971F5-7FB1-47E9-BDCA-8EE206328488@.microsoft.com...
> >I am running a report that is using a stored proc that has been changed. I
> > made the changes that I am aware of however there seems to be a field
> > somewhere in an expression that causes this error ... I cannot figure out
> > how
> > to locate the field!
> > It doesnt tell me what expression or what field. The error occurs in
> > report
> > preview and the text is this:
> >
> > An error occurred during local report processing.
> > an unexpected error occurred in the report processing.
> > the expression referenced a non-existing field in the fields collection.
> >
> >
>
>|||Yes, Check the syntax in the stored proc, if you want to post it, I'll look
at it as well.
I ran in to this same problem last week. I altered a stored proc and all of
a sudden I was getting this error, found that I had put an
ISNULL(tbl.FieldName, 0) and it came back to SQL Reports as an unknown
field. As soon as I made it ISNULL(tb.FIeldName,0) as 'CurrentValue' the
field was no longer a problem in SQL Reports.
"MJT" <MJT@.discussions.microsoft.com> wrote in message
news:7249105D-B46E-40BB-B468-DCC97C47A767@.microsoft.com...
> are you saying that I should check the stored procedure? I am not using
> sql.
> I have verified that all the fields are coming back from the stored
> procedure and exist in the fields collection so this is very strange.
> "Chris" wrote:
>> Double check your SQL. If you have something that you have wrapped with
>> a
>> function (ie. LTRIM(tbl.Field), this will not have a fields name. You
>> would need to do: LTRIM(tbl.Field) as FieldName
>> Hope that helps
>> "MJT" <MJT@.discussions.microsoft.com> wrote in message
>> news:E98971F5-7FB1-47E9-BDCA-8EE206328488@.microsoft.com...
>> >I am running a report that is using a stored proc that has been changed.
>> >I
>> > made the changes that I am aware of however there seems to be a field
>> > somewhere in an expression that causes this error ... I cannot figure
>> > out
>> > how
>> > to locate the field!
>> > It doesnt tell me what expression or what field. The error occurs in
>> > report
>> > preview and the text is this:
>> >
>> > An error occurred during local report processing.
>> > an unexpected error occurred in the report processing.
>> > the expression referenced a non-existing field in the fields
>> > collection.
>> >
>> >
>>|||this may be a bit of an interesting dilemma. I will let you know the
outcome. I am combining 2 reports into one report. Each report seems to run
successfully one its own. When I put them together and run them ... I get
that error. The interesting part is that the 2 reports use the same stored
procedure however they return different result sets depending on the
parameter values sent. I have 2 separate datasets set up and 2 separate
tables set up to render the data so in theory this should work from what I
have read. I am wondering if I am running into an issue where it somehow
*thinks* a field is missing because it exists in one result set and not the
other? I am reworking this solution again ... step by step to see at what
point it fails. As of now I have each separate report working and I am about
to combiine them again. I will post again. Thanks for your help ... that is
still a possibility (the stored procs) and I will keep that in mind ... I
have to involve another group for that so I need to verifiy the point of
failure first.
"Chris" wrote:
> Yes, Check the syntax in the stored proc, if you want to post it, I'll look
> at it as well.
> I ran in to this same problem last week. I altered a stored proc and all of
> a sudden I was getting this error, found that I had put an
> ISNULL(tbl.FieldName, 0) and it came back to SQL Reports as an unknown
> field. As soon as I made it ISNULL(tb.FIeldName,0) as 'CurrentValue' the
> field was no longer a problem in SQL Reports.
>
>
> "MJT" <MJT@.discussions.microsoft.com> wrote in message
> news:7249105D-B46E-40BB-B468-DCC97C47A767@.microsoft.com...
> > are you saying that I should check the stored procedure? I am not using
> > sql.
> > I have verified that all the fields are coming back from the stored
> > procedure and exist in the fields collection so this is very strange.
> >
> > "Chris" wrote:
> >
> >> Double check your SQL. If you have something that you have wrapped with
> >> a
> >> function (ie. LTRIM(tbl.Field), this will not have a fields name. You
> >> would need to do: LTRIM(tbl.Field) as FieldName
> >>
> >> Hope that helps
> >>
> >> "MJT" <MJT@.discussions.microsoft.com> wrote in message
> >> news:E98971F5-7FB1-47E9-BDCA-8EE206328488@.microsoft.com...
> >> >I am running a report that is using a stored proc that has been changed.
> >> >I
> >> > made the changes that I am aware of however there seems to be a field
> >> > somewhere in an expression that causes this error ... I cannot figure
> >> > out
> >> > how
> >> > to locate the field!
> >> > It doesnt tell me what expression or what field. The error occurs in
> >> > report
> >> > preview and the text is this:
> >> >
> >> > An error occurred during local report processing.
> >> > an unexpected error occurred in the report processing.
> >> > the expression referenced a non-existing field in the fields
> >> > collection.
> >> >
> >> >
> >>
> >>
> >>
>
>|||what i will do is to re create the report layout from scratch since there is
no problem in stored procedure. it may be a reason that you wrongly copied
some expression from another report and it is difficult to point to the
expression where it occurs. There is no debugger for the expression code. if
you assemblie you can debug easily to find the syntax error in the code.
~Bava
"MJT" wrote:
> this may be a bit of an interesting dilemma. I will let you know the
> outcome. I am combining 2 reports into one report. Each report seems to run
> successfully one its own. When I put them together and run them ... I get
> that error. The interesting part is that the 2 reports use the same stored
> procedure however they return different result sets depending on the
> parameter values sent. I have 2 separate datasets set up and 2 separate
> tables set up to render the data so in theory this should work from what I
> have read. I am wondering if I am running into an issue where it somehow
> *thinks* a field is missing because it exists in one result set and not the
> other? I am reworking this solution again ... step by step to see at what
> point it fails. As of now I have each separate report working and I am about
> to combiine them again. I will post again. Thanks for your help ... that is
> still a possibility (the stored procs) and I will keep that in mind ... I
> have to involve another group for that so I need to verifiy the point of
> failure first.
> "Chris" wrote:
> > Yes, Check the syntax in the stored proc, if you want to post it, I'll look
> > at it as well.
> > I ran in to this same problem last week. I altered a stored proc and all of
> > a sudden I was getting this error, found that I had put an
> > ISNULL(tbl.FieldName, 0) and it came back to SQL Reports as an unknown
> > field. As soon as I made it ISNULL(tb.FIeldName,0) as 'CurrentValue' the
> > field was no longer a problem in SQL Reports.
> >
> >
> >
> >
> > "MJT" <MJT@.discussions.microsoft.com> wrote in message
> > news:7249105D-B46E-40BB-B468-DCC97C47A767@.microsoft.com...
> > > are you saying that I should check the stored procedure? I am not using
> > > sql.
> > > I have verified that all the fields are coming back from the stored
> > > procedure and exist in the fields collection so this is very strange.
> > >
> > > "Chris" wrote:
> > >
> > >> Double check your SQL. If you have something that you have wrapped with
> > >> a
> > >> function (ie. LTRIM(tbl.Field), this will not have a fields name. You
> > >> would need to do: LTRIM(tbl.Field) as FieldName
> > >>
> > >> Hope that helps
> > >>
> > >> "MJT" <MJT@.discussions.microsoft.com> wrote in message
> > >> news:E98971F5-7FB1-47E9-BDCA-8EE206328488@.microsoft.com...
> > >> >I am running a report that is using a stored proc that has been changed.
> > >> >I
> > >> > made the changes that I am aware of however there seems to be a field
> > >> > somewhere in an expression that causes this error ... I cannot figure
> > >> > out
> > >> > how
> > >> > to locate the field!
> > >> > It doesnt tell me what expression or what field. The error occurs in
> > >> > report
> > >> > preview and the text is this:
> > >> >
> > >> > An error occurred during local report processing.
> > >> > an unexpected error occurred in the report processing.
> > >> > the expression referenced a non-existing field in the fields
> > >> > collection.
> > >> >
> > >> >
> > >>
> > >>
> > >>
> >
> >
> >|||thanks for your suggestion ... I would re-create from scratch but the report
is rather complicated so it would be best to try it this way first before
trying to reinvent the wheel. I still suspect it has something to do with
the fact that I am calling the same stored proc twice somehow although like I
said ... the result sets are feeding two different data regions.
"Bava Mani" wrote:
> what i will do is to re create the report layout from scratch since there is
> no problem in stored procedure. it may be a reason that you wrongly copied
> some expression from another report and it is difficult to point to the
> expression where it occurs. There is no debugger for the expression code. if
> you assemblie you can debug easily to find the syntax error in the code.
> ~Bava
> "MJT" wrote:
> > this may be a bit of an interesting dilemma. I will let you know the
> > outcome. I am combining 2 reports into one report. Each report seems to run
> > successfully one its own. When I put them together and run them ... I get
> > that error. The interesting part is that the 2 reports use the same stored
> > procedure however they return different result sets depending on the
> > parameter values sent. I have 2 separate datasets set up and 2 separate
> > tables set up to render the data so in theory this should work from what I
> > have read. I am wondering if I am running into an issue where it somehow
> > *thinks* a field is missing because it exists in one result set and not the
> > other? I am reworking this solution again ... step by step to see at what
> > point it fails. As of now I have each separate report working and I am about
> > to combiine them again. I will post again. Thanks for your help ... that is
> > still a possibility (the stored procs) and I will keep that in mind ... I
> > have to involve another group for that so I need to verifiy the point of
> > failure first.
> >
> > "Chris" wrote:
> >
> > > Yes, Check the syntax in the stored proc, if you want to post it, I'll look
> > > at it as well.
> > > I ran in to this same problem last week. I altered a stored proc and all of
> > > a sudden I was getting this error, found that I had put an
> > > ISNULL(tbl.FieldName, 0) and it came back to SQL Reports as an unknown
> > > field. As soon as I made it ISNULL(tb.FIeldName,0) as 'CurrentValue' the
> > > field was no longer a problem in SQL Reports.
> > >
> > >
> > >
> > >
> > > "MJT" <MJT@.discussions.microsoft.com> wrote in message
> > > news:7249105D-B46E-40BB-B468-DCC97C47A767@.microsoft.com...
> > > > are you saying that I should check the stored procedure? I am not using
> > > > sql.
> > > > I have verified that all the fields are coming back from the stored
> > > > procedure and exist in the fields collection so this is very strange.
> > > >
> > > > "Chris" wrote:
> > > >
> > > >> Double check your SQL. If you have something that you have wrapped with
> > > >> a
> > > >> function (ie. LTRIM(tbl.Field), this will not have a fields name. You
> > > >> would need to do: LTRIM(tbl.Field) as FieldName
> > > >>
> > > >> Hope that helps
> > > >>
> > > >> "MJT" <MJT@.discussions.microsoft.com> wrote in message
> > > >> news:E98971F5-7FB1-47E9-BDCA-8EE206328488@.microsoft.com...
> > > >> >I am running a report that is using a stored proc that has been changed.
> > > >> >I
> > > >> > made the changes that I am aware of however there seems to be a field
> > > >> > somewhere in an expression that causes this error ... I cannot figure
> > > >> > out
> > > >> > how
> > > >> > to locate the field!
> > > >> > It doesnt tell me what expression or what field. The error occurs in
> > > >> > report
> > > >> > preview and the text is this:
> > > >> >
> > > >> > An error occurred during local report processing.
> > > >> > an unexpected error occurred in the report processing.
> > > >> > the expression referenced a non-existing field in the fields
> > > >> > collection.
> > > >> >
> > > >> >
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >|||I have tried running the parts of the report separately and they work ... I
put them together and they dont ... I get the "expression referenced a
non-existing field in the fields collection" error message and report wont
run. Since both run separately I am not inclined to think it is stored proc.
Any more ideas?
"Chris" wrote:
> Yes, Check the syntax in the stored proc, if you want to post it, I'll look
> at it as well.
> I ran in to this same problem last week. I altered a stored proc and all of
> a sudden I was getting this error, found that I had put an
> ISNULL(tbl.FieldName, 0) and it came back to SQL Reports as an unknown
> field. As soon as I made it ISNULL(tb.FIeldName,0) as 'CurrentValue' the
> field was no longer a problem in SQL Reports.
>
>
> "MJT" <MJT@.discussions.microsoft.com> wrote in message
> news:7249105D-B46E-40BB-B468-DCC97C47A767@.microsoft.com...
> > are you saying that I should check the stored procedure? I am not using
> > sql.
> > I have verified that all the fields are coming back from the stored
> > procedure and exist in the fields collection so this is very strange.
> >
> > "Chris" wrote:
> >
> >> Double check your SQL. If you have something that you have wrapped with
> >> a
> >> function (ie. LTRIM(tbl.Field), this will not have a fields name. You
> >> would need to do: LTRIM(tbl.Field) as FieldName
> >>
> >> Hope that helps
> >>
> >> "MJT" <MJT@.discussions.microsoft.com> wrote in message
> >> news:E98971F5-7FB1-47E9-BDCA-8EE206328488@.microsoft.com...
> >> >I am running a report that is using a stored proc that has been changed.
> >> >I
> >> > made the changes that I am aware of however there seems to be a field
> >> > somewhere in an expression that causes this error ... I cannot figure
> >> > out
> >> > how
> >> > to locate the field!
> >> > It doesnt tell me what expression or what field. The error occurs in
> >> > report
> >> > preview and the text is this:
> >> >
> >> > An error occurred during local report processing.
> >> > an unexpected error occurred in the report processing.
> >> > the expression referenced a non-existing field in the fields
> >> > collection.
> >> >
> >> >
> >>
> >>
> >>
>
>