Programming a date field

[Richie27]

Hi all,



I need help please.

I need to create a program in access which, upon putting in a date in a particular field, there is another date field which is calculated based on the date that was primarily input.

The calculated field will be 10 years from the input date.

Also, would it be possible to have a timer that counts down from ten years once the first date has been input?

Any advice or opinions on this would be great....deadlines are looming!

Thanks in advance!

[June7]

Calculations can't be done in tables (unless you want to buy Access 2010). Do calculations in queries or in textboxes on forms/reports or in code. A timer for 10 years - can't even imagine that. You can do a query that will filter for records that meet given date criteria.

Check out date functions in Access Help or review this http://www.techonthenet.com/access/functions/

[Richie27]

Calculations can't be done in tables (unless you want to buy Access 2010). Do calculations in queries or in textboxes on forms/reports or in code. A timer for 10 years - can't even imagine that. You can do a query that will filter for records that meet given date criteria.

Check out date functions in Access Help or review this http://www.techonthenet.com/access/functions/

I know calculations in tables are a bad idea. Ya, I thought the timer thing sounded a bit crackers myself - clients making demands though, ya know - weren't happy with the query, filter thing!

[June7]

Could have code that would run automatically when project opens and check records against the age criteria and then popup a message or form or report.

[Richie27]

Sounds like something worth pondering that does. no idea where to start wit& that but will definitely have a think about it. Cheers!

[June7]

Could be an autoexec macro or VBA behind a form that is set by project properties to open on default.

[Richie27]

Could be an autoexec macro or VBA behind a form that is set by project properties to open on default.

Hey, thanks again for the idea.

I was just wondering about one thing though.

I previously build an access 2007 database on a Windows xp operating system and did some basic coding and macros, which worked as expected.

However, when I copied the file on to a Windows 7 machine, a lot of my code and macros did not work properly anymore.

So, what I am wondering is this - is it reasonable to expect code or macros that I program now to work several operating systems down the line??

I realise that xp came out before access 2007 so I was thinking that the code not working was related to the fact that windows 7 came out after access 2007.

What are your thoughts on this?

I'm a big fan of keeping things simple and think the date/query filter thing is by far the best option.


Thanks again.

.

[June7]

I haven't used Windows 7 yet but I have seen other postings discussing issues with Access 2007 running under it. Think I might be able do some testing next week.

I think it's reasonable to expect Microsoft programs to run forever under any future MS operating system. But I'm just a user, MS might not share my opinion.