Results 1 to 5 of 5
  1. #1
    Join Date
    Sep 2002
    Posts
    3

    Unanswered: access 97: this expression is typed incorrectly, or is too complex to be evaluated...

    SQL for query is:

    SELECT CLIENT.AUD_NAME, CLMINFO.VEND_NBR, VENDCODE.VEND_NAME,
    [DivisionList]![Abrev2] & "C" & Right([CLMINFO]![CLAIM_NBR],6) AS
    CLAIM_NUM, PAYBACK.PYBCK_AMT, [CLMINFO]![DATE_ENTRD]-7 AS [DATE WRITTEN],
    IIf([CLMINFO]![DATE_DEDCT]>#10/1/2001#,"CCM","FOOD") AS [FOOD/CCM]
    FROM (((CLMINFO INNER JOIN VENDCODE ON (CLMINFO.CLIENT_NBR =
    VENDCODE.CLIENT_NBR) AND (CLMINFO.VEND_NBR = VENDCODE.VEND_CODE)) INNER
    JOIN CLIENT ON CLMINFO.AUD_NBR = CLIENT.AUD_NBR) INNER JOIN DivisionList
    ON CLIENT.AUD_NBR = DivisionList.[audit number 2001]) INNER JOIN PAYBACK
    ON CLMINFO.CLAIM_KEY = PAYBACK.CLAIM_KEY
    WHERE (((PAYBACK.PYBCK_DATE)=Date()));

    I came in and ran this report one day and it came up with the message:

    This expression is typed incorrectly, or is too complex to be evaluated.
    For example, a numeric expression may contain too many complicated
    elements. Try simplifying the expression by assigning parts of the
    expression to variables.

    Now when I take out the criteria Date() the error goes away. The other
    problem is that my "Right([CLMINFO]![CLAIM_NBR],6)" is just returning
    #Error (I just tried evaluating that part of the expression and that is
    where I was getting the error). I've already tried some of the reference
    fixes, but that has not worked. I have also tried SR-2b and the
    Jet35sp3. Just curious if anyone knows any other options or is familiar
    with this problem?

  2. #2
    Join Date
    Jul 2002
    Posts
    67
    I encountered a similar situation a while ago but my problem was caused because Access 2000 was installed on the same machine as Access 97 and some of the .dll's became corrupt.

    Have you done anything out of the ordinary on your machine in the last few days. i.e: install/uninstall software? Does the .mdb work on another computer? If it does, than your application is fine and the problem lies elsewhere.

    I know this doesn't solve your problem. Do keep us posted on your progress.
    Don't do today, what can be done tomorrow.

  3. #3
    Join Date
    Sep 2002
    Posts
    3
    No....In fact, I formatted my drive, installed windows2K and office 97 only, and it wouldn't work. The query does work on another computer. Just kind of at a loss right now :-S

  4. #4
    Join Date
    Aug 2002
    Location
    Charlotte NC
    Posts
    665
    I ran into this problem when my expresion was too long for the text box I was putting it in (ie on a report etx.) that is the only time that I have seen that.
    Regards Jim

  5. #5
    Join Date
    Sep 2002
    Posts
    3
    Fixed the problem......sort of!!!!
    I still can not get the original one to work.....although others can, but I imported the old database into a new Db and it works fine now.....

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •