Search results

  1. F

    Confusing Dates Query

    One more problem... Using the code: Private Sub Year_End_Date_GotFocus() mydate = Date 'set to system date 'yearend = Forms![booking in]![booking in lookup sub]![year end (dd/mm)] yearend = Me.[booking in lookup sub]![year end (dd/mm)] MsgBox (yearend) If mydate < DateValue(yearend) Then...
  2. F

    Confusing Dates Query

    Actually, I did think of that too but was confusing my poor old grey matter and I'm less than half your age! ;) All working now though so can get some of the people who are going to be using this to start testing it. No doubt the minute I stop working here they'll do something stupid and mess...
  3. F

    Confusing Dates Query

    It works But the "then" and "else" are the wrong way round! ;) :p Thanks so much though! :D
  4. F

    Confusing Dates Query

    Cheers! Might be better if you just post the amended database since you have it working. Saves me hassle! :D
  5. F

    Confusing Dates Query

    Well I'll change the field names at some time then to remove all the spaces and hopefuly that can stop any potential problems. Might also get rid of the (dd/mm) in the Year End (dd/mm) field name too as that is getting a bit confusing as well. Oh yeah, I forgot to mention the subform :o I...
  6. F

    Confusing Dates Query

    Attachment Attached with a very limited amount of sample data. Thanks.
  7. F

    Confusing Dates Query

    Thanks I've got the query working, after a few adjustments as you've missed out a couple of little bits. No probs though as it's working. Just thought I'd mention it incase anyone else is looking at this thread or looks at it in future. ;) The final code for the query is...
  8. F

    Confusing Dates Query

    Me posting again Ok, I've decided the best way around this problem is for the Booking In table (data entered from a form) to require the field for year end date. What I want it to do is simply automatically put in the year end for the records in (which can then be overwritten if needed) once a...
  9. F

    Confusing Dates Query

    I've got the query working mostly apart from what I said in my last post about how it can't check the current year end against the most recent records received, i.e. If I have two sets of records for a client with a year end 5th April, one for year end 05/04/03 and one for 05/04/04 and then...
  10. F

    Confusing Dates Query

    I'm nearly there with: SELECT Clients.[Client Code], Clients.[Client Name], Clients.[Trading As Name], Clients.[Client Type], IIf((Now()>DateValue([Year End (dd/mm)])),DateValue([Year End (dd/mm)]),(DateValue([Year End (dd/mm)])-365)) AS [Year end], [Records Received].[Year End Date] Although...
  11. F

    Confusing Dates Query

    Hmm, I see. That could solve the problem..... Enter date as text and use a query to convert it to date using current year. Then my query would work as I could ask to match year end date with this converted date as long as the date falls within the last 365 days. That should make sense. Will...
  12. F

    Confusing Dates Query

    I did fear that much. Is there any way to remove the year part of the date in the Clients Database otherwise in a years time or so the data is all going to be messed up.
  13. F

    Confusing Dates Query

    I am trying to set up a database for an accounts firm I am working for using Access XP. The database is being used to keep track of clients’ records and the progress of their accounts. The database consists of a number of tables recording various pieces of information: Clients Table: - Client...
Back
Top Bottom