Seeking Design Advice

14 Jul 2006 1:59 PM

Jerry

Hello!

I'm creating an application where users can enter their hours worked on
certain projects and have them saved to a database. Right now there are
about 60 different projects and that number can increase or decrease at
any time.

I'm looking for some advice on how to best design the windows form for
users to enter hours for the projects they worked on that week. I was
thinking about using a comboBox to list each project with a text box to
enter hours. The user would be presented with update and save buttons.
The update button would save the current project's hours to a class and
the save button would write all the saved info to the database. Is
there a better way to do this?

I apologize for posting such a trivial question. This is my first real
VB.NET application so it's still a learning process :-)

--
Jerry

16 Jul 2006 3:51 PM

AK

Jerry,

RE: Saving to a class -

Maybe I am missing something, but wouldn't you want to add the current hours
to the project hours and save that to the database? Or better yet have the
database keep the log of the days and hours worked and the worker that
worked them, from which a query could be run at will or at run time (say in
a manegement function report module) to accumulate and report the hours.

AK

Show quoteHide quote

"Jerry" <jerrya***@gmail.com> wrote in message
news:1152885559.549401.190660@35g2000cwc.googlegroups.com...
> Hello!
>
> I'm creating an application where users can enter their hours worked on
> certain projects and have them saved to a database. Right now there are
> about 60 different projects and that number can increase or decrease at
> any time.
>
> I'm looking for some advice on how to best design the windows form for
> users to enter hours for the projects they worked on that week. I was
> thinking about using a comboBox to list each project with a text box to
> enter hours. The user would be presented with update and save buttons.
> The update button would save the current project's hours to a class and
> the save button would write all the saved info to the database. Is
> there a better way to do this?
>
> I apologize for posting such a trivial question. This is my first real
> VB.NET application so it's still a learning process :-)
>
> --
> Jerry
>

17 Jul 2006 1:55 PM

Jerry

Currently they add their total hours to an Excel spreadsheet on a
weekly basis. They would like to continue on that same schedule and
process but would like to use a VB.NET application to store the data in
the database instead of the spreadsheet.

--
Jerry

AK wrote:

Show quoteHide quote

> Jerry,
>
> RE: Saving to a class -
>
> Maybe I am missing something, but wouldn't you want to add the current hours
> to the project hours and save that to the database? Or better yet have the
> database keep the log of the days and hours worked and the worker that
> worked them, from which a query could be run at will or at run time (say in
> a manegement function report module) to accumulate and report the hours.
>
> AK
>
>
> "Jerry" <jerrya***@gmail.com> wrote in message
> news:1152885559.549401.190660@35g2000cwc.googlegroups.com...
> > Hello!
> >
> > I'm creating an application where users can enter their hours worked on
> > certain projects and have them saved to a database. Right now there are
> > about 60 different projects and that number can increase or decrease at
> > any time.
> >
> > I'm looking for some advice on how to best design the windows form for
> > users to enter hours for the projects they worked on that week. I was
> > thinking about using a comboBox to list each project with a text box to
> > enter hours. The user would be presented with update and save buttons.
> > The update button would save the current project's hours to a class and
> > the save button would write all the saved info to the database. Is
> > there a better way to do this?
> >
> > I apologize for posting such a trivial question. This is my first real
> > VB.NET application so it's still a learning process :-)
> >
> > --
> > Jerry
> >

17 Jul 2006 8:56 PM

raibeart

You need to learn about database design.

You need to design it like a database and show it to them like an Excel
file.

If you do not do this, why bother? Just have a common spreadsheet and
still save it there. Then when the whole thing comes tumbling down,
and it will, you can say, "I told you it should be a database."

If you need help with the database design, I will help with that.

Show quoteHide quote

> AK wrote:
> > Jerry,
> >
> > RE: Saving to a class -
> >
> > Maybe I am missing something, but wouldn't you want to add the current hours
> > to the project hours and save that to the database? Or better yet have the
> > database keep the log of the days and hours worked and the worker that
> > worked them, from which a query could be run at will or at run time (say in
> > a manegement function report module) to accumulate and report the hours.
> >
> > AK
> >
> >
> > "Jerry" <jerrya***@gmail.com> wrote in message
> > news:1152885559.549401.190660@35g2000cwc.googlegroups.com...
> > > Hello!
> > >
> > > I'm creating an application where users can enter their hours worked on
> > > certain projects and have them saved to a database. Right now there are
> > > about 60 different projects and that number can increase or decrease at
> > > any time.
> > >
> > > I'm looking for some advice on how to best design the windows form for
> > > users to enter hours for the projects they worked on that week. I was
> > > thinking about using a comboBox to list each project with a text box to
> > > enter hours. The user would be presented with update and save buttons.
> > > The update button would save the current project's hours to a class and
> > > the save button would write all the saved info to the database. Is
> > > there a better way to do this?
> > >
> > > I apologize for posting such a trivial question. This is my first real
> > > VB.NET application so it's still a learning process :-)
> > >
> > > --
> > > Jerry
> > >

18 Jul 2006 1:34 PM

Jerry

raibeart wrote:

> You need to learn about database design.
>
> You need to design it like a database and show it to them like an Excel
> file.
>
> If you do not do this, why bother? Just have a common spreadsheet and
> still save it there. Then when the whole thing comes tumbling down,
> and it will, you can say, "I told you it should be a database."
>
> If you need help with the database design, I will help with that.

Thanks. I already know database design. The information entered in the
application will be saved to a database. I'm just looking for the best
way to design the application.

--
Jerry