Results 1 to 4 of 4
  1. #1
    Join Date
    Oct 2003
    Posts
    233

    Unanswered: overhead and speed or other issues about using a qry

    I have a field i need to add to a report. this field exist in a qry, that has other fields i dont need. the qry is nested on about 5 or so qrys. If i add a field to my report, and just use the 1 field from this qry will that bring over head, slow down or cause any other issues? the field has a ton of logic and iff statements and calculations. I would rather just add the field rather than create a qry only creating this 1 field, any thoughts?

  2. #2
    Join Date
    Jan 2007
    Location
    UK
    Posts
    11,434
    Provided Answers: 10
    Why not write a separate simple query for the one field as apposed to using your beast? Alternatively, the domain aggregate functions (DCount, DMax, DSum, etc...) are your friends!
    George
    Home | Blog

  3. #3
    Join Date
    Oct 2003
    Posts
    233
    thats exactly what i did Thanks!

  4. #4
    Join Date
    May 2005
    Location
    Nevada, USA
    Posts
    2,888
    Provided Answers: 6
    Does that mean the solution posted on your other thread worked?
    Paul

Posting Permissions

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