Search results

All sorted. I actually resolved this while working on another DB. It's just DateAdd not outputting things as a date, I don't know why... So although probably not the "proper" way for it to be done I just put it into a field of it's own and then that obviously formats it properly this then...

I'll have a play. Thanks for your help!

Why when I add 1 month to ReportDate does it not go from 1/12/2011 to 1/1/2012 instead it jumps to 1/7/2013 - that's ultimately what I'm asking.

Thanks for the help but I ended up finding the answer. Incase anyone else wants to do something similar you'll need this: Date() - WeekDay(Date()) + 1 - which is explained somewhat here: http://www.techonthenet.com/access/functions/date/weekday.php

Hi, I have an update query whereby if it matches criteria it updates a date using dateadd which looks like the following: DateAdd("m",1,[ReportDate]) Now for some reason it updates it to 01/07/2013 (ReportDate was set as 01/12/2011) - I have no idea why because the criteria for the update...

Hi, So what I'm looking at doing is getting dates for the current weeks Monday and Saturday. I think what I'd need to do is look at todays date say that came back as Thursday 19/1/2012, I then would want it to get me Monday's date and Saturday's date and put them in the necessary field for...

Ahh of course! I will make the necessary changes. I actually noticed while having a play that it works fine if I take out the totalused + used part of the query. I'll give it a try and see what it does, thanks buddy. EDIT: Works fine now, thank you. I'm so silly for missing this lol.

As requested, please find the link below. Many thanks :) http://dl.dropbox.com/u/9551747/StockTest.accdb

Yeah it is set to date/time. Please find attached a screenshot showing how it's setup.

It's entered manually and set to use short date, so it shouldn't have a time part to it. Sorry for the late reply.

There is only one row for it to look at in that table though. There are three fields, two yes/no fields and the ReportDate field which currently contains the date of 1/10/2011, this means it falls into the correct criteria for the update query to work... well it should lol. I attached a picture...

Nopes, I guess that's not good.

Yes, sorry. For some reason that post above decided to cut half of what I said off. I tried it and it did not update the necessary fields implying it didn't work. To be clear about exactly what I have in the query, I have attached a picture. Thanks again.

Thanks for your reply. The thing with using that is I need to use a stored date and that's going to change once a month. So can I do the DateAdd and use a field? So DateAdd("m",1,[StoredDate]) with the criteria of

Hey, So basically I have a update query whereby I have a stored date that I want to compare against today's date and if it's smaller, then update some fields. Now I want it to actually be a month later than the stored date so something like this: [StoredDate]+31 < Date() then... blabla. For...

Give up, formatting won't stick it and it makes it incredibly difficult to explain. Please delete.

This was something I was unaware of but I do only want it on single selection and it is set to this. With regards to the bound column - what should this be set to? It is set to 1, I've never used list boxes before so unsure of the properties that well. I'm hoping I can get it sorted coming back...

So basically I've got a couple of tables setup like so: tblGroup: GroupID Group tblStudent: Student Number Usual stuff, firstname, lastname etc. tblGroupLink: StudentNumber GroupID Primary Group What I want to do is setup a form that has a list box containing the groups and then select one...

Yeah, I believe the problem lies with some old data that isn't up to date and doesn't need to actually be in the database. It's on my to do list to remove it but for now the Null value issue shouldn't be too much of a problem (hopefully). I think I've sorted a workaround anyway by inputting 0...

What you have posted seems to have done the trick. Thank you very much :) Perhaps it worked due to some of the warranty fields being blank?