Newbies richards Posted January 22, 2009 Newbies Posted January 22, 2009 We have been having a problem where relationships using < or > in them slow down creating new records and in some cases replace statements. Does anyone have any advice?
RalphL Posted January 22, 2009 Posted January 22, 2009 We have been having a problem where relationships using < or > in them slow down creating new records and in some cases replace statements. Does anyone have any advice? What is the purpose of creating records with < or > relationships? How many records do you want to create? I suggest that you use = relationships to create a single related record. Again with Replace use =.
Newbies richards Posted January 22, 2009 Author Newbies Posted January 22, 2009 What is the purpose of creating records with < or > relationships? How many records do you want to create? I suggest that you use = relationships to create a single related record. Again with Replace use =. More Information: File1 - Table1 Relationship Example: Orders::AccountNo = Orders::AccountNo Orders::Date > Orders::Date Used to find the Order previous to the current Order for the AccountNo. Problem #1: Slow down when creating a new record. Problem #2: Slow down during replaces on some fields that are not necessarily associated with the relationship.
RalphL Posted January 23, 2009 Posted January 23, 2009 More Information: File1 - Table1 Relationship Example: Orders::AccountNo = Orders::AccountNo Orders::Date > Orders::Date Used to find the Order previous to the current Order for the AccountNo. Problem #1: Slow down when creating a new record. Problem #2: Slow down during replaces on some fields that are not necessarily associated with the relationship. The relationship you show is incorrect, it should look something like: Orders::AccountNo = Orders1::AccountNo AND Orders::Date > Orders1::Date I assume you are using a portal to show the results. This is a query relationship and should not have anything to do with creation of new records. However there will be time required to gather the information for the portal when the AccountNo & Date are entered.
Newbies richards Posted January 23, 2009 Author Newbies Posted January 23, 2009 The relationship you show is incorrect, it should look something like: Orders::AccountNo = Orders1::AccountNo AND Orders::Date > Orders1::Date I assume you are using a portal to show the results. No portal, using the relationship to get information on the previous order on file for the AccountNo. Example: New Record is created and has a text calculated stored field that grabs the first character of a field on the previous order for the AccountNo. This is a query relationship and should not have anything to do with creation of new records. However there will be time required to gather the information for the portal when the AccountNo & Date are entered.
Recommended Posts
This topic is 5842 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 accountSign in
Already have an account? Sign in here.
Sign In Now