Recent content by littlelegs

  1. L

    "SELECT TOP n" and "UNION"

    Tried it and the sql is working much better, still have a few anomalies... but the results are more what I expected. Thanks again...
  2. L

    "SELECT TOP n" and "UNION"

    Thanks - I was going to reply that I needed to have the LEVEL ranked for the award but then realized it doesn't matter because of eligiblity checking earlier on. So I will try to remove the ORDER BY stmt and see what happens - Thanks muchly!
  3. L

    "SELECT TOP n" and "UNION"

    I want to end up with a recset with 6 recs in it - 3 at one level and 3 at the next level. Wouldn't UNION first then SELECT TOP 3 give me a recset with only 3 recs? Forgive me, if I am not seeing the obvious... )
  4. L

    "SELECT TOP n" and "UNION"

    I am hoping someone can help me with the following statement: SELECT TOP 3 * FROM RIDSCORE WHERE ((RIDSCORE.RIDER_L) = "LEWANDOWSKI") And ((RIDSCORE.RIDER_F) = "Amanda") And ((RIDSCORE.LEVEL) = "B1" ) ORDER BY RIDSCORE.LEVEL UNION SELECT TOP 3 * FROM RIDSCORE WHERE ((RIDSCORE.RIDER_L) =...
  5. L

    'SELECT TOP n' and 'UNION' sql statement

    I am hoping someone can help me with the following statement: SELECT TOP 3 * FROM RIDSCORE WHERE ((RIDSCORE.RIDER_L) = "LEWANDOWSKI") And ((RIDSCORE.RIDER_F) = "Amanda") And ((RIDSCORE.LEVEL) = "B1" ) ORDER BY RIDSCORE.LEVEL UNION SELECT TOP 3 * FROM RIDSCORE WHERE ((RIDSCORE.RIDER_L) =...
  6. L

    sub and temp query

    Thanks very much for your very good advice. I hadn't considered the implications of the usage of specific words for field names. Most of my problems have arisen because of importing the tables from a (yech!!) db3 format.... as well a ton of data (non)integrity issues... So I renamed the year...
  7. L

    public vs dim

    When/what are the most appropriate uses for either Dim or Public? Why one over the other?
  8. L

    sub and temp query

    Hope someone here can help me... I keep getting run-time error '3061 - Too few parameters, expected one' on the 'Set class_rst = ' line of the following sub. I went and had a look the article mentioned previously about '3061' but it wasn't any help as it seemed to deal with permanent queries...
  9. L

    Query Expression where one field is greater than another

    are they in the same table? If so then you should be able to use/build an expression in the criteria on the total_amt field, something like: >= access_amt (looks easy but then again... maybe i'm missing something... ) )
  10. L

    temporary queries

    Hope someone here can help me... I keep getting run-time error '3061 - Too few parameters, expected one' on the 'Set class_rst = ' line of the following sub: Sub Get_horse_recs(class_rst, class) sql_string = "" RIDER_F = query_rst(0) RIDER_L = query_rst(1) l1 = "SELECT * " l2 =...
Back
Top Bottom