Join1
  Home FAQ Contact Sign in
 
Advanced search
MATCHING GROUPS



more...
POPULAR GROUPS

more...

found 4 articles for 0.297 sec
We have been using the eConnect_Out_Setup table to detect changes within Great Plains for a number of versions. When creating our standard objects into the latest version (10) though, Great Plains Utilities errors out on the salesorder trigger. Just to clarify -- inserting the objects into the database works fine. The problem arises when GP Utilities updates the database. Here is the     

Group: uk.rec.competitions · Group Profile · Search for Join1 in uk.rec.competitions
Author: Deb
Date: Nov 29, 2007 12:50

Forgot to say - if you do want to have the Loan Description field showing with Items being entered more than once if they appear more than once in Table 2, then have a calculated query with all of Table 2 and Loan Description from the Loan Table (call it eg QryLoanAndItems). Add this query to a new query along with the query you produced when joining all the 3 tables together (we'll call it QryResult
Show full article (0.04Kb)
I've just tried it out and I can see the problem. If you have one of those Join 2's (Left Joins) in a query then you can't always have a normal Join1 (Inner Join) as well, so any other tables that need to be joined together need to be joined first in another query. You problem is that while each item only appears once in each of the other tables, does it appear more than once in the Table2?     

Group: microsoft.public.greatplains · Group Profile · Search for Join1 in microsoft.public.greatplains
Author: Steve
Date: Nov 28, 2007 12:33

Show full article (3.42Kb)
    

Group: microsoft.public.access.formscoding · Group Profile · Search for Join1 in microsoft.public.access.formscoding
Author: Evi
Date: May 18, 2007 21:32

Show full article (2.63Kb)
    

Group: microsoft.public.access.formscoding · Group Profile · Search for Join1 in microsoft.public.access.formscoding
Author: Evi
Date: May 18, 2007 07:43

Show full article (1.83Kb)