Recent content by luckycharms

  1. L

    Rename cell based on duplicate compound key

    Hi Pat, Thanks for the reply. When I say "portable", I mean portable to different DB systems. An access form, for example, won't be portable to a MYSQL db, for example. Neither will VBA. Interesting that Access is able to interact via ODBC - didn't know that, and it'd be interesting to look...
  2. L

    Rename cell based on duplicate compound key

    Hi Jeanette, Thanks for your response, and I totally understand your sentiment. I *greatly* appreciate the time, effort and expertise that volunteers like MStef graciously share! Perhaps I mis-worded my response to MStef. Let my clarify what I meant when I said "something not so...
  3. L

    Rename cell based on duplicate compound key

    Thanks so much for your help! While it seemed to work for me, I was looking for a solution that wasn't so "Access-centric". I ended up scripting a solution that worked on an excel file.
  4. L

    Rename cell based on duplicate compound key

    Hi Folks, I'm trying to rename a cell when there are duplicates of mutliple columns. Here's an example Col_1 Col_2 Col_3 Note A1 B1 C1 A1 B2 C1 Not a Dup A1 B1 C2 Not a Dup A2 B2 C2 A2 B2 C2 Duplicate A3...
  5. L

    Specifying the data type of a calculated column in a SELECT

    You are not understanding my point, and I think it's because you're living in an Access-GUI-centric world. User access to queries (aka views) is not just via form or report. They can be accessed via ODBC for example, as I mentioned above, or via ResultSet in VBA. Neither one of those methods...
  6. L

    Specifying the data type of a calculated column in a SELECT

    spikepl, i'm sorry you're feeling frustrated. The truth is that I feel the same way; i.e., you're not getting what i'm saying. I understand that you're trying to distinguish between the display format and data type. I agree with you - a display can show any one data type in many different...
  7. L

    Specifying the data type of a calculated column in a SELECT

    Displayed in the datasheet view. Not sure why you think queries are not to be looked at. In any case, the datatype that Access considers that column to be is important. I will be pulling data out of access using ODBC, into other programs, and it will probably be important that Access consider...
  8. L

    Specifying the data type of a calculated column in a SELECT

    I wanted the column displayed as checkboxes. I thought that if Access considered the column to be a boolean data type, it would display them with checkboxes.
  9. L

    Specifying the data type of a calculated column in a SELECT

    the *result* of the IsNull() operation is boolean, but i'm not sure if the data type of the column in the result set is boolean. I'm not totally sure how to check that, though. Perhaps I'd have to do a SELECT INTO instead of a SELECT, or something like that. Perhaps there's a better way...
  10. L

    Specifying the data type of a calculated column in a SELECT

    the resulting column is composed of "0"s and "-1"s. Were it boolean, it would have checkboxes I think.
  11. L

    Specifying the data type of a calculated column in a SELECT

    the following still doesn't seem to give me a boolean in the result set: Select CBool(NOT(IsNull(a.ID))) as aMatch, a.*, b.* FROM TableA a RIGHT JOIN TableB b ON a.ID = b.ID
  12. L

    Specifying the data type of a calculated column in a SELECT

    i'm interested in the isNull(a.ID) column being a boolean. As it stands, it's numeric (or text - i can't tell which).
  13. L

    Specifying the data type of a calculated column in a SELECT

    taruz, thanks for the reply, but i don't quite catch your drift...
  14. L

    Specifying the data type of a calculated column in a SELECT

    Hi Folks, I'm doing something like the following: Select NOT(IsNull(a.ID)) as aMatch, a.*, b.* FROM TableA a RIGHT JOIN TableB b ON a.ID = b.ID However, the "aMatch" column resulting from the query is either numeric or text. Is there any way I can specify that the resulting column should be a...
Back
Top Bottom