Program techniques : change indexorder or use aliases
Posted: Mon Nov 02, 2020 3:15 pm
I wonder what the best technique would be and the advantages of 1 of the 2
Often, I need to use the same database in more than one lookup action or update action.
1. I can change the index order, but than I also have to keep track of resetting it back and at the correct position
2. I can open de database in more aliases and use different browses and lookups with these aliases ?? Can I get issues with the CDX file ?
And we can use Oop (James), smaller parts are converted somethimes in this way.
But just out of interest... witch is used more often here ( 1 or 2) ?
In 1 : The first time, sometimes is with a relation set to ... , and when the database order is changed, the relation is broken. (I believe this is standard in FW)
Often, I need to use the same database in more than one lookup action or update action.
1. I can change the index order, but than I also have to keep track of resetting it back and at the correct position
2. I can open de database in more aliases and use different browses and lookups with these aliases ?? Can I get issues with the CDX file ?
And we can use Oop (James), smaller parts are converted somethimes in this way.
But just out of interest... witch is used more often here ( 1 or 2) ?
In 1 : The first time, sometimes is with a relation set to ... , and when the database order is changed, the relation is broken. (I believe this is standard in FW)