CH 12 LoadTimeSheet() Problem

chuck · #1 (**permalink**) November 29th, 2005, 11:23 PM

I am having a problem in CH 12 - trying to log in as a user returns the following error:

Code:

Operator is not valid for type "Integer" and type "DBNULL"

The error is returned at this line of code from TimeSheet.vb:

Code:

intTotal += objTimeSheetDS.Tables( _
                "TimeSheet").Rows(intIndex).Item("MondayHours")

I believe it is looking for rows of data that do not exist in the DB.

I am using the code downloaded from Wrox.com.

Any help with this would be appreciated - This problem is identical to the 2nd problem posted in this forum (hgcheong), but that solution will not help in this case as I have not typed the code for the solution and can assume that the code is correct.

Chuck

chuck · #2 (**permalink**) November 30th, 2005, 07:23 AM

Additional - just completely installed everything needed for the Time Tracker project on my home computer (other post was in regards to work computer) and I get the same error. Am able to add users using the Command Window method on Pages 348-349. When I attempt to logon as User1, I get the same error at home that I did at work. As before, I am using the code from the book, so it is not a typo error.

Operator is not valid for type "Integer" and type "DBNULL"

Anyone have any ideas?

Chuck

chuck · #3 (**permalink**) November 30th, 2005, 09:35 AM

If anyone has the time, could you shoot me a quick screen shot of valid data for the TimeSheets and TimeSheetItems tables, then I can be on my way, and I will return the favor if I can someday.

Chuck

chuck · #4 (**permalink**) January 22nd, 2006, 09:44 AM

I still need the answer to this problem, I put it on the back burner until I get the code to continue.

Chuck

Thearon · #5 (**permalink**) January 23rd, 2006, 07:29 AM

Chuck,

You should never run across an instance where the employee does not have a timesheet. Check the GetTimeSheet procedure in the WDATimeSheets class in the data access component. This procedure checks the DataSet after you call the usp_SelectTimeSheet stored procedure and if it is empty, it calls the AddTimeSheet procedure to insert an empty timesheet.

Thearon

jaulven · #6 (**permalink**) February 11th, 2006, 08:15 PM

Thearon,
I'm having this same problem in Chap. 12(Private Sub LoadTimeSheet). The problem is that when it queries the new time sheet record (usp_SelectTimeSheets)after it gets added to the TimeSheets table, it looks for an integer value for "MondayHours" in the objTimeSheetsDS RecordSet, but finds a NULL value. That's where the error occurs.
Was there a spot I'm missing that converts these NULLS to zeros?
Please help!
Thanks.
John

* The book has been great so far!

Thearon · #7 (**permalink**) February 14th, 2006, 08:06 PM

You'll need to set a breakpoint on the line of code:

objTimeSheetDS = objTimeSheets.GetTimeSheet( _
New Guid(strUserID), WeekEndingDate.SelectedItem)

in the LoadTimeSheet procedure and trace this call through line by line to determine where the problem lies.

When you get to the GetTimeSheet procedure in the WDATimeSheets class, ensure the UserID and WeekEndingDate parameters contain values.

Thearon

druss000 · #8 (**permalink**) November 2nd, 2006, 09:14 AM

Just downloaded code from site and is experiencing the same problem. Did not see a resolution to this problem in previous responses. Thus, how do I resolve this issue?

Thearon · #9 (**permalink**) November 6th, 2006, 07:07 AM

When you installed SQL Server, did you perform a default installation of SQL Server or did you customize the installation options?

Thearon

PisithOum · #10 (**permalink**) April 22nd, 2010, 01:41 AM

Dear chuck,

How this issue solve?

Best Regards,

Thanks

Pisith Oum

Need to download code?

Navigation