Recent content by kkjewell

  1. K

    join properties cause type mismatch

    Bob, thank you so much. I can't believe it was something that small. I was so sure it was a really advanced problem way above my head. Why would that only show up when I changed the join statement. Seems like it should never have run in the first place. Anyway, thanks again, Kathy
  2. K

    join properties cause type mismatch

    Okay the first attempt at getting it to you created 2.2M file after zipping it. I had to laugh. Anyway, now I've taken out everything except the tables and queries you need and it's still 2,223K. Any suggestions?
  3. K

    join properties cause type mismatch

    Sure, however I'm sure the linked tables won't work once I send it somewhere. Also I'm not sure how to attach it. The attachment button below says it supports several file types, but .mdb is not one of the options. Should I just attach it anyway or is there another way to send it to you.
  4. K

    join properties cause type mismatch

    sorry I had to go to a meeting so am just getting back to this Yes they were joined before and worked fine. At that time the History table what the "first" table. Now literally the only change was to make Master the first table. By "first" I mean the one to which the query looks to pull all...
  5. K

    join properties cause type mismatch

    I understand, but the only change I have made at all is the change in the join statment between the two tables, so the mismatch has to be that there is no data in the second (History) table. Absolutely nothing else changed.
  6. K

    join properties cause type mismatch

    Okay, I apologize, I'm not extremely Access knowledgeable so bear with me. I have an Access database I created which I thought was working okay, then I realized it was missing one vendor because we haven't started writing checks to that vendor yet and probably won't for a while. I am using a...
  7. K

    simple question :)

    subreport solution Ben, use "sorting and grouping" to make sure you have a header and footer for your individuals. Create a subreport for the summation query (the one that has the totals for each individual). Insert the subreport into the main report (there's a button that will prompt a...
  8. K

    Report requests parameter value

    Found my own answer Report was based on a query that contained two tables. Several of the fields had the same name, because they were the same field in both tables. When I set up the relationship between the tables I only tied the key field. When Access was running the report it couldn't...
  9. K

    Report requests parameter value

    Hello ... by problem: Explanation: Table has a single field (AllocAmt) that is repeated for each detail transaction. Therefore I can't put the sum of the single field on the report because it adds that sum times the count of the detail. The solution I attempted was to create a subreport...
  10. K

    Report requests parameter value

    Sorry Sorry, I didn't realize I was posting it in FAQ, where should I post it?
  11. K

    Report requests parameter value

    Hello ... by problem: Explanation: Table has a single field (AllocAmt) that is repeated for each detail transaction. Therefore I can't put the sum of the single field on the report because it adds that sum times the count of the detail. The solution I attempted was to create a subreport...
Back
Top Bottom