By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,442 Members | 1,368 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,442 IT Pros & Developers. It's quick & easy.

Week Numbers

P: n/a
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
Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
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." <ad*******@yahoo.com> wrote in message
news:cb**************************@posting.google.c om...
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

Nov 13 '05 #2

P: n/a
"Larry Linson" <bo*****@localhost.not> wrote in
news:fw*******************@nwrddc02.gnilink.net:
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
Larry, I was about to ask the same questions, then realized it's
July.


"A.G." <ad*******@yahoo.com> wrote in message
news:cb**************************@posting.google.c om...
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



--
Bob Quintal

PA is y I've altered my email address.
Nov 13 '05 #3

P: n/a
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 <rq******@sPAmpatico.ca> wrote in message news:<Xn**********************@66.150.105.50>...
"Larry Linson" <bo*****@localhost.not> wrote in
news:fw*******************@nwrddc02.gnilink.net:
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

Larry, I was about to ask the same questions, then realized it's
July.


"A.G." <ad*******@yahoo.com> wrote in message
news:cb**************************@posting.google.c om...
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


Nov 13 '05 #4

P: n/a
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." <ad*******@yahoo.com> wrote in message
news:cb**************************@posting.google.c om...
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 <rq******@sPAmpatico.ca> wrote in message

news:<Xn**********************@66.150.105.50>...
"Larry Linson" <bo*****@localhost.not> wrote in
news:fw*******************@nwrddc02.gnilink.net:
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

Larry, I was about to ask the same questions, then realized it's
July.


"A.G." <ad*******@yahoo.com> wrote in message
news:cb**************************@posting.google.c om...
> 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

Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.