how do select on select with sql - and how do prevent dublicate record

Question

2.33/5 (2 votes)

See more:

hi all

in my organizer program (with csharp and access)

Question 1 :
i have a table in access with this structure :

work_name ---- for my work name
work_date ---- date that i shoud do work
work_time ---- time that i shoud do work
work_alarm --- day number that i get Warning or alarm

for example :

i want go to univercity in 2013/5/12 in time 15:30 and i want get alarm in 3 days before this work

i save this to table like below :
work_name = go to univercity
work_date = 2013/5/12
work_time = 13:30
work_alarm = 3

now Suppose i have a 500 record that any one have a different date and time ....

i want a selet that do below porpuse :
warning or alarm for all work According to
1-current date (system date)
2-work_date
3-work alarm

Question 2 :
i not found any stored procedure or query whit input and output parameter in access
how do i prevent when insert a record ?

thanks a lot

Posted 7-May-13 7:40am

Esmaeil Ebrahimi

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2013-05-07T08:23:00

Personally, I wouldn't do it that way: I would probably store it as a pair of DateTime objects:
Work_Date and Alarm_date - and set the Alarm date based on the selected time interval when the user inserts it. That way, the database doesn't need to know what range of intervals your application is interested in - 15 minutes is the same as 7 days to the database. In addition, the calculation is made once, and in "human time" when the appointment is set up. With your scheme the alarm time has to be calculated each time you want to check it.

In your application, you just read out all appointments due in the next hour (say) with a simple SQL every half hour, and you get a list of alarms you should respond to straight away.

Question 2 makes no sense whatsoever to me, so I can't even begin to answer it.

BTW: Have you annoyed someone? Your questions appear to have been down voted en bloc.