Jump to content
Sign in to follow this  
The Big Bear

date range solution???

Recommended Posts

Hi all

My company needs to track when welders weld with the welding process they are qualified in. This needs to be recorded once every six months. I have script a auto range find. This finds welder one month before thier qualifiaction are expired. The way the script works it that the range starts the day the button is push then adds 30 days. So, If the range date button is push on 7/12/2007. Then the range is 7/12/2007 to 8/12/2007. This find all the welder between those dates. Then we known who to update. The problem is if the button is push 7/12/2007 and the welder are updated and then push again on 7/20/2007. Some of the welder that were update still appears.

Example

buttom push 7/12/2007

range 7/12/2007 to 8/12/2007

welder are updated

button push again on 7/20/2007

range 7/20/2007 to 8/20/2007

some of the same welders are appears if they were updated . Because their second to last date still falls into the date range.

I have tried to find a solution to this from over a year but with no succes.

Any help will be greatly appriecated.

Lionel ;)

Share this post


Link to post
Share on other sites

I'm not sure I completely understand you, but it sounds like perhaps you need an additional field to track the last update date (or "next update date") and include that in your search criteria.

I guess I don't understand why you're even searching for people in the same date range. If you run the script once daily, or weekly or monthly, you wouldn't get overlapping found sets.

Share this post


Link to post
Share on other sites

Fitch

Thanks for the answer. I understand about pressing the expiration button only once a month but the weld program is use by people at different location and someone always calls and says that that part of the program is not working. After getting more information from the user, they push the expiration button two or more times in that month.

I was looking for away of when the wekder is updated then he will not appear in the expiration report again if someone else presses the expiration button.

Thanks

Lionel

Share this post


Link to post
Share on other sites

I think the idea proposed above will work: as part of your "update" process, set a field that represents "do not update before this date." Then, as part of your search script, omit records where "do not update" > "date range end".

Using your example:

button push 7/12/2007

- range: 7/12/2007 to 8/12/2007

- welder are updated;

+ "do not update" is set to 9/12/2007

button push again on 7/20/2007

- range: 7/20/2007 to 8/20/2007;

+ new request: "do not update" > 8/20/200, Omit

Result: the welder updated on 8/12 will be omitted from the found set.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use.