Recent content by Voltron

  1. Voltron

    System Resource Exceeded

    What I'm looking for is not to sum up the numbers in the columns, but there should be only 1 cell that has a numerical value out of the 3 possible for each row.
  2. Voltron

    System Resource Exceeded

    I completely understand. Thank you for all of your help to this point.
  3. Voltron

    System Resource Exceeded

    Unfortunately, I cannot upload anything. It is set to Group By because this is what it defaulted to. There are some queries where I need to use Total: Sum so I click the crosstab button and then click back to Select and it keeps it on there and lets me do a Select query. Most of the queries...
  4. Voltron

    System Resource Exceeded

    Would it just make more sense to do it where each fee has its own query? I know how to do that with the new setup of the database, but this is driving me insane.
  5. Voltron

    System Resource Exceeded

    Sorry. Missed your post.
  6. Voltron

    System Resource Exceeded

    Got it. That was painless.
  7. Voltron

    System Resource Exceeded

    Have to download winzip first.
  8. Voltron

    System Resource Exceeded

    I'm trying to update my queries, but it is not working properly. I have 3 fees that multiply the total assets by a given percentage. The percentage is in the ClientFees_TBL and is given for each of the fees. Total Assets is located in another query and is easily accessible. There are multiple...
  9. Voltron

    System Resource Exceeded

    I have another question as to the design of the new database. With the fees they can be dollar amounts, percentages, or Yes/No checkboxes (which are used for some of the queries that are based 100% off of other queries). Would I need to create 3 separate ClientFees_TBL tables to get the desired...
  10. Voltron

    System Resource Exceeded

    Thank you very much for that explanation. That is something that I had forgotten, but makes perfect sense. I can see where the rows will significantly reduce work down the road and make life much easier. Hopefully the rows based structure will resolve the complexity issue that Access is having...
  11. Voltron

    System Resource Exceeded

    Ok, but why is that? If you have a group of "things" (such as fees) then you should have them in their own table so you can combine them with another table (clients) that way?
  12. Voltron

    System Resource Exceeded

    In what way is it not normalized right now? Based off of the knowledge you currently have, I realize you can't see the whole database. I realize that database design is a huge issue and am working on improving my understanding. I am currently taking your suggestions. I have been the whole...
  13. Voltron

    System Resource Exceeded

    Makes sense. I've been tinkering and found out it has to do with the "cancel" and "reversal" queries. Why they are needed is unimportant. These are set up the same was as the Fee Summary queries (Part 1, Part 2, and Total). However, there are 3 separate ones (1 for each type of revenue) for...
  14. Voltron

    System Resource Exceeded

    I understand the table structure you are referring to. The problem is I don't understand why the database isn't working the way it is now. I have not reach any known limit on anything that I can see. The only thing I can think of is this: 3 primary queries (Part 1, Part 2, Total). Part 1 +...
  15. Voltron

    System Resource Exceeded

    No. You're right. You are definitely barking up the correct tree.
Back
Top Bottom