Search results

  1. A

    A Tale of Two Tables

    Great direction, thanks for your guidance on this process. It's as you said: the hard part is the beginning but if done right, it will be much less painful moving forward.
  2. A

    A Tale of Two Tables

    I understand that. I didn't design these tables; I inherited this data. One comes from SQL Server Reporting Services and the other from an in-house application. Each time I do the data pulls, the data comes to me that way. I have to merge these two on a regular basis so I was hoping for help on...
  3. A

    A Tale of Two Tables

    I have one table TestDataFcstTime_97.xls where time was forecasted for some projects we're working on. The second table TestDataActualTime_97.xls is the time that was actually recorded for projects. In the forecasted table, the weeks are the column headings; in the Actual table the weeks are...
  4. A

    Year Over Year Variance #Error

    Worked perfectly! Thanks
  5. A

    Year Over Year Variance #Error

    I am trying to do a very simple calculation in a query to determine year over year variance displayed as a percentage: TotYoYVar%: ([2016FcstTotal]-[2015Total])/[2015Total] How can I prevent Access from returning a result of #Error when [2015Total] is 0?
  6. A

    Can There Be Too Many Parameters?

    Thanks, I know this is basic Access table design 101, but I was trying to do a "quick & dirty" query based on am Excel file. Clearly there are no shortcuts.
  7. A

    Can There Be Too Many Parameters?

    Below is a simple parameter query that I created, however the end users don't think it is useful as is. What they'd like to see is the current parameter to remain in place, but also to be able to select any combination of months for comparison. In other words, for example, what if I (the end...
  8. A

    Import from Salesforce into Access

    Excellent advice Doc_Man! My thoughts exactly
  9. A

    Import from Salesforce into Access

    Seems odd to me too, but a couple days ago, I was told by Tech Support that the Salesforce api is something they don't allow.
  10. A

    Import from Salesforce into Access

    No choice about Salesforce--it is our enterprise wide CRM application. It's up to me to figure out how to get the data I need from it, in the most efficient way possible
  11. A

    Import from Salesforce into Access

    When you say export to a .csv or similar, do you mean via a manual process? Because that is what I am doing now: I run a report in SFDC, export it to Excel, then import that file from Excel to Access. In order to get even close to realtime, I would have to repeat this process each time. It...
  12. A

    Import from Salesforce into Access

    Yes, that's above my altitude. Thanks
  13. A

    Import from Salesforce into Access

    I generate reports in Salesforce that then have to be exported to Excel then imported into Access 2007 (yes, I know...we are STILL using 2007), but I am looking to cut out the middleman by importing directly from Salesforce into Access 2007? What is the process?
  14. A

    Design Changes to an ACCDE

    @pbaldy I'm sure it is design issues, due to my lack of knowledge on how to address the changes my team wants via query design. Every month, the most current revenue that had been previously forecasted is now closed and in the books so it is data that is no longer housed in the Assumptions...
  15. A

    Design Changes to an ACCDE

    So I've created my DB, split it, housed the backend on a shared drive, and converted the frontend to an ACCDE file. Each month, I will need to make small changes to the design of about 5 of the queries before refreshing the data. What's the best way to do this? I'm pretty sure I don't have to...
  16. A

    Front End Bloat Keeps Happening

    So it's probably the macros/make-table queries I have: I went to a saved copy of the DB, deleted the 3-4 tables that I didn't need, then split the DB. The front end was less than 2MB! I was thrilled. But before emailing it out, I wanted to be sure all would go well; after running the macros in...
  17. A

    Front End Bloat Keeps Happening

    What I see are the following: MSysAccessXML MSysACEs MSysIMEXColumns MSysIMEXSpecs MSysObjects MSysQueries MSysRelationships and that's it
  18. A

    Front End Bloat Keeps Happening

    @cyanide No MSysResources table showed up, but Thanks for trying.
  19. A

    Front End Bloat Keeps Happening

    I should have said it is not a single-user DB. There will be multiple users accessing it.
  20. A

    Front End Bloat Keeps Happening

    I will check for img files. Everything I've read advises against automatically compacting the DB on close when it is not a single-use DB, and mine is not.
Top Bottom