Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > Visual Basic > VB.NET 1.0 > BOOK: Beginning VB.NET Databases
Password Reminder
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
BOOK: Beginning VB.NET Databases
This is the forum to discuss the Wrox book Beginning VB.NET Databases by Thearon Willis; ISBN: 9780764568008
Welcome to the p2p.wrox.com Forums.

You are currently viewing the BOOK: Beginning VB.NET Databases section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old April 4th, 2005, 03:17 AM
Registered User
Join Date: Dec 2004
Location: Newbury, Berks, United Kingdom.
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Default HasRows problem using Visual Studio 2002

I am following the example using Visual Studio 2002, and have had the "HasRows" problem Which occurs on page 104, and 132 there may be other pages, I haven't got that far yet!

My question is, how was this issue tackled before the "HasRow" property was added? In other words what is the correct way to return the number of rows in Visual Studio 2002?

I realize that this is not necessary for the example, but if possible, I would like to have the code working perfectly.

Any response or comment Appreciated.

Reply With Quote
  #2 (permalink)  
Old April 4th, 2005, 03:55 AM
Thearon's Avatar
Wrox Author
Join Date: Dec 2003
Location: Fuquay Varina, NC, USA.
Posts: 396
Thanks: 0
Thanked 8 Times in 8 Posts

The HasRows property is merely a nice property to quickly determine if the DataReader contains any data to be read. Before the HasRows property you actually had to invoke the Read method of the DataReader and go through your logic and test to see if the DataReader returned any data.

As you can see, the HasRows property merely cuts out a few steps in your processing making your application more effeicent.

Reply With Quote
  #3 (permalink)  
Old April 12th, 2005, 08:14 AM
Registered User
Join Date: Dec 2004
Location: Newbury, Berks, United Kingdom.
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts

It's OK, I got it licked! I have upgraded to Visual Studio 2003.....!

Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Visual Studio .net2003 and Visual Studio 2005 Gert Visual C++ 1 January 24th, 2006 05:10 AM
Visual Studio 2002 server explorer and toolbox iss songsan General .NET 0 December 21st, 2004 03:56 PM
Visual Studio 2002 Vs. 2003 psmothers BOOK: Professional SQL Server Reporting Services ISBN: 0-7645-6878-7 2 September 13th, 2004 09:52 PM
Visual Studio problem viking25 C# 0 October 18th, 2003 06:19 AM
Accessing Mappoint 2002 via Visual Studio .NET 200 ThomasN VS.NET 2002/2003 3 August 19th, 2003 01:46 PM

All times are GMT -4. The time now is 09:25 PM.

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