Search results

  1. R

    VBA query selecting records outside of date range

    Gemma-the-husky, Thanks for your reply. That's an interesting point. I guess I think of it as a string because there is a date mask on the input field and I think you can only mask a string. However, it does act like a date, so I'm not sure......
  2. R

    VBA query selecting records outside of date range

    JHB, Thanks so much for your reply. The piece of code worked in both Win 8 and Win 7. I guess because Format() converts it to a string, as spikepl explained, it needed to happen within the SQL statement. Thanks again.
  3. R

    VBA query selecting records outside of date range

    txtStartDate is a string. In Win 7 it shows as dd-mm-yyyy. In Win 8 it shows as yyyy-mm-dd. So I don't think dateserial will work for the Win 7 version.
  4. R

    VBA query selecting records outside of date range

    spikepl, Sorry, I thought my syntax for "Format" and "CDate" might be wrong. Here are the relevant functions. Private Sub cmdCityRep_Click() Dim dteStart As Date Dim dteEnd As Date If IsNull(Me.txtStartDate) Or IsNull(Me.txtEndDate) Then MsgBox "Please enter date range" Else dteStart...
  5. R

    VBA query selecting records outside of date range

    Thanks all for your help. The Allen Browne article was a big help. It now seems to work in Win 7 changing the date format from dd-mm-yyyy to mm-dd-yyyy and using that in the SQL statement, however, it now does not work in Win 8.1. The Format function does not seem to change the yyyy-mm-dd...
  6. R

    Copying a Record contain Multi-Value field

    Thanks, Ted. Your code worked beautifully!
  7. R

    VBA query selecting records outside of date range

    I’ve run into an extremely bizarre problem. I have written a program using Access 2010 on a Win 8.1 machine. The default regional date setting is yyyy-mm-dd. When I run the VBA queries to find records that have a start date between a user input date range it works fine. The problem occurs...
  8. R

    Table Design

    That's what I thought at first, however, after thinking about it I think I only need to have the information that doesn't change to be in the client table and all else to be in case table. Then create a 1:M relationship from client to case. No, but there could be multiple cases per client.
  9. R

    Table Design

    Thanks, jdraw. I will review the literature and see what I can come up with.
  10. R

    Table Design

    Thanks for replying, It has over 100 fields because that is the requirement by the shelter and the interested parties. They need to capture, retain and report on all of this data. The type of information they wish to collect are things like: demographic information (gender, ethnicity...
  11. R

    Table Design

    I’m working on a project for a homeless shelter. They need to keep track of a lot of information and generate a number of reports for the various interested parties. When a client requests aid in finding a permanent residence a “case” is created, whereby, the necessary information is captured...
  12. R

    Hello from Canada

    I'm an experienced programmer but have not used Access in quite some time and seem to have forgotten quite a bit. I'm currently working on a project that requires an Access database be built but am running into some difficulties. I'm hoping that this forum can help me out. Thanks, in advance...
Top Bottom