"CGW" <CGW@discussions.microsoft.com> wrote in message
news:CA85A1DA-9CE9-443F-9AC5-0A374086029E@microsoft.com...
> Actually, it helped with most toggled textboxes, but not those within
> tables.
> Toggling columns, however, does work, but with one small problem. I
> haven't
> identified yet what determines it, but in the same table, some columns
> will
> toggle off certain textboxes outside the table, but not others; while
> other
> columns in the same table will not toggle off the same textboxes as the
> first
> columns, but will off different ones.
>
> I'm not sure how understandable that is, but if VS refuses to preview a
> report because of a toggle problem on a column, simply try toggling the
> column off a different textbox.
>
> Thank you for your help, Brian. I think I've got it working now... after a
> fashion.
>
> "Brian Welcker [MS]" wrote:
>
>> No, the hotfix was only for expression-based visibility, not toggling. I
>> don't understand exactly your scenario so I can't offer a workaround. If
>> this is essential for you, the best way to work is through product
>> support.
>> Or you can post a repro here but we can't promise that it will get fixed.
>>
>> --
>> Brian Welcker
>> Group Program Manager
>> Microsoft SQL Server
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "CGW" <CGW@discussions.microsoft.com> wrote in message
>> news:D440F5E1-8950-47B2-9819-65F42BB12AD8@microsoft.com...
>> > The hotfix I was able to get from MS support was only partially
>> > successful.
>> > Regular textboxes within the body of the report, which were hidden, now
>> > remain hidden upon rendering to Excel. However, textboxes within
>> > tables,
>> > within the same report body and toggling on the same textbox, do not
>> > remain
>> > hidden.
>> >
>> > Is it possible that there is another, later hotfix that deals with this
>> > problem as well? Or, alternately, is there something else I can do to
>> > take
>> > care of it.
>> >
>> > Thanks
>> >
>> > "CGW" wrote:
>> >
>> >> Thank you! What's the best way to contact product support to ask for
>> >> the
>> >> hot
>> >> fix?
>> >>
>> >> "Brian Welcker [MS]" wrote:
>> >>
>> >> > This is a bug in SP1 and will be fixed in SP2. It is available as a
>> >> > hotfix
>> >> > if you need it immediately. You can contact product support to get
>> >> > the
>> >> > hotfix (you will not be charged).
>> >> >
>> >> > --
>> >> > Brian Welcker
>> >> > Group Program Manager
>> >> > Microsoft SQL Server
>> >> >
>> >> > This posting is provided "AS IS" with no warranties, and confers no
>> >> > rights.
>> >> >
>> >> > "CGW" <CGW@discussions.microsoft.com> wrote in message
>> >> > news:51145687-EDA8-4F0E-AFF3-8CE3FD2E17F0@microsoft.com...
>> >> > > I'm having two problems with exports to Excel and hope that
>> >> > > someone
>> >> > > can
>> >> > > help.
>> >> > > Our reports are straightforward (tables, few matrices, nothing
>> >> > > nested).
>> >> > > They
>> >> > > each contain textboxes who's visibility is toggled and are
>> >> > > switched
>> >> > > to
>> >> > > hidden=false before export. However, no matter how we work it,
>> >> > > they
>> >> > > show
>> >> > > up
>> >> > > in the exported spreadsheet, though they are no longer visible in
>> >> > > the
>> >> > > report.
>> >> > >
>> >> > > And the second problem is that extra, merged columns are showing
>> >> > > up;
>> >> > > columns
>> >> > > which are not in the original report. It plays havoc with sorts.
>> >> > >
>> >> > > Help would be greatly appreciated. We have tons of reports and I
>> >> > > don't
>> >> > > want
>> >> > > to have to switch to Crystal or programmatic solutions if we can
>> >> > > avoid it.
>> >> > > --
>> >> > > Thanks,
>> >> > >
>> >> > > CGW
>> >> >
>> >> >
>> >> >
>>
>>
>>

"Brian Welcker [MS]" wrote:

> This is a bug in SP1 and will be fixed in SP2. It is available as a hotfix
> if you need it immediately. You can contact product support to get the
> hotfix (you will not be charged).
>
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "CGW" <CGW@discussions.microsoft.com> wrote in message
> news:51145687-EDA8-4F0E-AFF3-8CE3FD2E17F0@microsoft.com...
> > I'm having two problems with exports to Excel and hope that someone can
> > help.
> > Our reports are straightforward (tables, few matrices, nothing nested).
> > They
> > each contain textboxes who's visibility is toggled and are switched to
> > hidden=false before export. However, no matter how we work it, they show
> > up
> > in the exported spreadsheet, though they are no longer visible in the
> > report.
> >
> > And the second problem is that extra, merged columns are showing up;
> > columns
> > which are not in the original report. It plays havoc with sorts.
> >
> > Help would be greatly appreciated. We have tons of reports and I don't
> > want
> > to have to switch to Crystal or programmatic solutions if we can avoid it.
> > --
> > Thanks,
> >
> > CGW
>
>