Wrox Programmer Forums
|
BOOK: Professional SQL Server Reporting Services ISBN: 0-7645-6878-7
This is the forum to discuss the Wrox book Professional SQL ServerReporting Services by Paul Turley, Todd Bryant, James Counihan, George McKee, Dave DuVarney; ISBN: 9780764568787
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Professional SQL Server Reporting Services ISBN: 0-7645-6878-7 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old June 18th, 2004, 09:06 AM
Authorized User
 
Join Date: Jun 2004
Posts: 50
Thanks: 0
Thanked 0 Times in 0 Posts
Default Chapter 7 p 214 code didn't work, changes needed..

I am working through the book (page by page, hence all the posts).

Currently I am working through Chapter 7, building a windows app that connects to the Reporting Services web service to manage reports.

On page 214 it tells us to create a new class and name it RSUtilities. It tells us to add system.io and [projectName].ReportingWebService

I had to also add:
System.Web.Services.Protocols

or I could not work with the Soap protocol.

If anyone else gets Soap related code errors showing up this may be what you need to do.

Using code on page 215 I got the following error:
C:\NetProjects\ReportServicesManager\ProfessionalS QLReportingServicesManager\MainForm.vb(298): 'ProfessionalSQLReportingServicesManager.RSUtiliti es.Private Shared Sub ErrorHandler(ex As System.Exception)' is not accessible in this context because it is 'Private'.

I changed the way I declared my sub to this:
Shared Sub ErrorHandler(ByVal ex As Exception)
and the error went away.

If this is not proper, please someone let me know.

Sandy Murdock MCP
__________________
Sandy Murdock MCP
 
Old June 20th, 2004, 09:06 PM
Friend of Wrox
 
Join Date: Jun 2003
Posts: 1,998
Thanks: 0
Thanked 3 Times in 3 Posts
Default

Hello,

You can declare Public, Friend(Internal in C#) or Protected if you needed to, although Friend and Protected may have the same problems. If it is a web service, that would make sense about the private context because outside programs couldn't access it when needed.

Brian





Similar Threads
Thread Thread Starter Forum Replies Last Post
Chapter 14 Code page 620, help needed! Safi BOOK: Beginning ASP 3.0 3 December 8th, 2010 12:43 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.