Jump to content

ExecuteSQL Relationship Issue?

This topic is 2743 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies

I need some help with ExecuteSQL.

I have a TO “Sales” that is related to Estimates, Inspections, and Proposals via ID_SALES:id_sales.

I created some simple ExecuteSQL calculations that work on Estimates and Inspections, but the same calculations will not work with the related Proposals TO. 

·         I know that the relationship is good because I can get the SUM and COUNT from Proposals with a basic calculation (not ExecuteSQL).

·         I know there is not a problem with the name on the related Proposals TO (like a space between words). I've copied and pasted the working calculations and I have started from scratch, and neither works.

This statement works:




"" ; "" ;

TO13_sales_ESTIMATES||id_sales::id_sales )


This statement does not work:




 "" ; "" ;



Any help would be appreciated.


Link to comment
Share on other sites

The fact that the relationships work on the FMS side is completely irrelevant once you use ExecuteSQL().  The SQL query does not use nor honor the FM relationships.  Which is a good thing because it gives all the flexibility.

When you say "this statement does not work", what is the result?  If the result is "?" then you have a syntax error in your query.  If the result is empty or a number that you don't expect then the query does something else than you expect.  Possibly because the context where you are on (the layout) when you run the query has no access to this field: TO13_sales_PROPOSALS||id_sales::id_sales



Link to comment
Share on other sites

This topic is 2743 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.