Initial Hypothesis: Create 4 connect web parts to allow users to submit their timesheets weekly. Also allow site collection administrators to submit timesheets for users. The web parts will also allow administrators to approve or reject the timesheet.Resolution: Create 4 connected web parts to display user timesheets on a page. Use the dialog framework to add and edit tasks. The ability to add a new task is done in another web part on a separate page. The edit task allows users to edit or delete and existing task, this is another custom web part place on a separate page within the site collection.

Create a web parts to perform basic administration options. I have create 3 administration web parts within Visual studio to allow administrators to update key timesheet information such as adding new client or projects or assigning people to a project.

Reporting for the timesheet can be created using either: Reporting Services and integrated into SharePoint, BCS to query data, or custom web parts.﻿

This looks like you connection string to your SQL instance is not correct.

In you Web.config in the "appSetting" section check the "ConnectionInfo" elements attribute settings. The post assumes you are using windows interated security of SQL Server and it's on the local machine. Ammend according to your environment.

Thanks Paul, you are right i fixed the connection string and its working, but the time sheet page is generating error which i think im missing the seed data. i noticed others having the same problem and trying the suggested solutions. tried to put some data in all tables but that didnt work, so im modifying the code.

i tried making the changes to the code to use SingleOrDefaul instead of Single and try catch still with no luck

here is the error im getting now

System.NullReferenceException: Object reference not set to an instance of an object. at PaulBeck.Timesheet.WebParts.Week.Week.get_GetWeekId() at PaulBeck.Timesheet.WebParts.BookTime.BookTime.ReceiveProvider(IWeekId p)