Week Numbers

**Larry Linson** · Nov 13 '05, 02:16 AM

Re: Week Numbers

There's nothing about the description of your table that would imply that it
would overwrite the old records. Presumably, you'll be generating the new
records with a new uniqueID (primary key?). However, if you search on
weeknumber, and start typing in over the data that is there, you are not
creating a new record, but editing the old one.

How is it that you are trying to enter the new records? From a Form? From
the datasheet view of the table? Other?

Please clarify so we can assist.

Larry Linson
Microsoft Access MVP

"A.G." <aditig526@yaho o.com> wrote in message
news:cbc65de0.0 407221245.1e94f 1b9@posting.goo gle.com...[color=blue]
> In our company we store employee hours by week number. We have a
> table called Time which has a unique id of TimeID and then other
> fields such as date, weeknumber, monday, tuesday, wednesday, etc...
> The problem is that at the end of the year when the week number goes
> back to 1, it begins to override the old data. We want to keep the
> old data. Is there a way so that I can me the year, timeID, and
> weeknumber unique? Thank you in advance.
>
> -ag[/color]

**Bob Quintal** · Nov 13 '05, 02:16 AM

Re: Week Numbers

"Larry Linson" <bouncer@localh ost.not> wrote in
news:fwXLc.3147 0$gt1.18291@nwr ddc02.gnilink.n et:
[color=blue]
> There's nothing about the description of your table that would
> imply that it would overwrite the old records. Presumably,
> you'll be generating the new records with a new uniqueID
> (primary key?). However, if you search on weeknumber, and
> start typing in over the data that is there, you are not
> creating a new record, but editing the old one.
>
> How is it that you are trying to enter the new records? From a
> Form? From the datasheet view of the table? Other?
>
> Please clarify so we can assist.
>
> Larry Linson
> Microsoft Access MVP
>[/color]
Larry, I was about to ask the same questions, then realized it's
July.

[color=blue]
>
> "A.G." <aditig526@yaho o.com> wrote in message
> news:cbc65de0.0 407221245.1e94f 1b9@posting.goo gle.com...[color=green]
>> In our company we store employee hours by week number. We
>> have a table called Time which has a unique id of TimeID and
>> then other fields such as date, weeknumber, monday, tuesday,
>> wednesday, etc... The problem is that at the end of the year
>> when the week number goes back to 1, it begins to override
>> the old data. We want to keep the old data. Is there a way
>> so that I can me the year, timeID, and weeknumber unique?
>> Thank you in advance.
>>
>> -ag[/color]
>
>
>[/color]

--
Bob Quintal

PA is y I've altered my email address.

**A.G.** · Nov 13 '05, 02:17 AM

Re: Week Numbers

Larry!

We use a form to enter the data, and you are correct it edits the
data, but I don't want it to edit. A user selects the dept, then
their name and then the weeknumber. Once these three thinks are
selected, the form activates all the tasks and work orders associated
with it. Then the user selects a project, and then work order and
then inputs the number of hours for a particular day. A new row is
created with uniqueID everytime a users selects a different project.
I hope this makes sense now, thank you for your help.

-ag

Bob Quintal <rquintal@sPAmp atico.ca> wrote in message news:<Xns952EC4 85F92D6BQuintal @66.150.105.50> ...[color=blue]
> "Larry Linson" <bouncer@localh ost.not> wrote in
> news:fwXLc.3147 0$gt1.18291@nwr ddc02.gnilink.n et:
>[color=green]
> > There's nothing about the description of your table that would
> > imply that it would overwrite the old records. Presumably,
> > you'll be generating the new records with a new uniqueID
> > (primary key?). However, if you search on weeknumber, and
> > start typing in over the data that is there, you are not
> > creating a new record, but editing the old one.
> >
> > How is it that you are trying to enter the new records? From a
> > Form? From the datasheet view of the table? Other?
> >
> > Please clarify so we can assist.
> >
> > Larry Linson
> > Microsoft Access MVP
> >[/color]
> Larry, I was about to ask the same questions, then realized it's
> July.
>
>[color=green]
> >
> > "A.G." <aditig526@yaho o.com> wrote in message
> > news:cbc65de0.0 407221245.1e94f 1b9@posting.goo gle.com...[color=darkred]
> >> In our company we store employee hours by week number. We
> >> have a table called Time which has a unique id of TimeID and
> >> then other fields such as date, weeknumber, monday, tuesday,
> >> wednesday, etc... The problem is that at the end of the year
> >> when the week number goes back to 1, it begins to override
> >> the old data. We want to keep the old data. Is there a way
> >> so that I can me the year, timeID, and weeknumber unique?
> >> Thank you in advance.
> >>
> >> -ag[/color]
> >
> >
> >[/color][/color]

**Larry Linson** · Nov 13 '05, 02:18 AM

Re: Week Numbers

You need to go to a new record... if you have the standard navigation
buttons on the bottom of the Form, click the rightmost one (solid arrowhead
and asterisk) and it will take you to a new record.

If you go to the existing record, it will, as you see, change it because
that is what you've asked it to do.

If you don't have the navigation buttons on the Form, you can create your
own, or more simply, in Design View, click the upperleftmost little square
on the Form, right Click, choose Properties and set Navigation

Larry Linson
Microsoft Access MVP

"A.G." <aditig526@yaho o.com> wrote in message
news:cbc65de0.0 407230957.4d13c 46e@posting.goo gle.com...[color=blue]
> Larry!
>
> We use a form to enter the data, and you are correct it edits the
> data, but I don't want it to edit. A user selects the dept, then
> their name and then the weeknumber. Once these three thinks are
> selected, the form activates all the tasks and work orders associated
> with it. Then the user selects a project, and then work order and
> then inputs the number of hours for a particular day. A new row is
> created with uniqueID everytime a users selects a different project.
> I hope this makes sense now, thank you for your help.
>
> -ag
>
> Bob Quintal <rquintal@sPAmp atico.ca> wrote in message[/color]
news:<Xns952EC4 85F92D6BQuintal @66.150.105.50> ...[color=blue][color=green]
> > "Larry Linson" <bouncer@localh ost.not> wrote in
> > news:fwXLc.3147 0$gt1.18291@nwr ddc02.gnilink.n et:
> >[color=darkred]
> > > There's nothing about the description of your table that would
> > > imply that it would overwrite the old records. Presumably,
> > > you'll be generating the new records with a new uniqueID
> > > (primary key?). However, if you search on weeknumber, and
> > > start typing in over the data that is there, you are not
> > > creating a new record, but editing the old one.
> > >
> > > How is it that you are trying to enter the new records? From a
> > > Form? From the datasheet view of the table? Other?
> > >
> > > Please clarify so we can assist.
> > >
> > > Larry Linson
> > > Microsoft Access MVP
> > >[/color]
> > Larry, I was about to ask the same questions, then realized it's
> > July.
> >
> >[color=darkred]
> > >
> > > "A.G." <aditig526@yaho o.com> wrote in message
> > > news:cbc65de0.0 407221245.1e94f 1b9@posting.goo gle.com...
> > >> In our company we store employee hours by week number. We
> > >> have a table called Time which has a unique id of TimeID and
> > >> then other fields such as date, weeknumber, monday, tuesday,
> > >> wednesday, etc... The problem is that at the end of the year
> > >> when the week number goes back to 1, it begins to override
> > >> the old data. We want to keep the old data. Is there a way
> > >> so that I can me the year, timeID, and weeknumber unique?
> > >> Thank you in advance.
> > >>
> > >> -ag
> > >
> > >
> > >[/color][/color][/color]

Week Numbers

Week Numbers

Comment

Comment

Comment

Comment