x Want to participate? Join the group to interact
Options
  • Replies 10 replies
  • Subscribers 120 subscribers
  • Views 1787 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
rclowe

Is an "Enforced Both Inner Join" type supported by the SOTAMAS90 ODBC DSN?

Posted By

I seem to recall a Sage KB that indicated there were only 3 Join Types supported by Sage (MAS, back in the day). Inner Join, Left Outer and something else. I don't recall hearing about the "Enforced" setting. I ask because we have a client who are very sharp and have created many new report and report settings. In this case they are linking in standard table into the work table using this join (which I have never before seen):

I can tell you that this report in its current state takes over 40 minutes to run and I think it is not running quick enough for Task Scheduler to send it to Microsoft's Print to PDF printer. Does that make sense?

TIA

Parents

  • Is it not possible to create a UDF for the BOM info?

  • in reply to BigLouie

    If not work table UDF's, a sub-report might be worth a try.

  • in reply to Kevin M

    Hey BL & KM,

    Both great suggestions, thanks - and tools in my toolbelt that I frequently use. However in this case I am not being asked to troubleshoot the report itself (yet), nor did I have a hand in creating it - so at this point I'm really just trying to gather info re this odd (IMHO) join type.

    I am also hoping to get some feedback on whether Task Scheduler might have a timeout feature for a report that takes a long time to run and send to PDF.

    If and when I'm asked to look deeper into the nuts and bolts of the report I will definitely try your suggestions. In fact, I just pulled this report over to take a look at and there don't appear to be any fields from BM_BillHeader anywhere on the report. Curiouser and curiouser..

Reply
  • in reply to Kevin M

    Hey BL & KM,

    Both great suggestions, thanks - and tools in my toolbelt that I frequently use. However in this case I am not being asked to troubleshoot the report itself (yet), nor did I have a hand in creating it - so at this point I'm really just trying to gather info re this odd (IMHO) join type.

    I am also hoping to get some feedback on whether Task Scheduler might have a timeout feature for a report that takes a long time to run and send to PDF.

    If and when I'm asked to look deeper into the nuts and bolts of the report I will definitely try your suggestions. In fact, I just pulled this report over to take a look at and there don't appear to be any fields from BM_BillHeader anywhere on the report. Curiouser and curiouser..

Children
  • in reply to rclowe

    I believe the enforced link is like a filter for items that have bills.  Without that option you'd have to put a filter for BillNo not being NULL (so the work table is generating data not being displayed... filtered by the enforced link). 

    A checkbox in items for "has a bill" should add an option in the Selection list and then Sage has to do less work in generating the report data.

  • in reply to Kevin M

    That makes sense, thanks again Kevin.

*Community Hub is the new name for Sage City