Hello,
I have a table in an app that has to be zapped as we move from job to job. I then pull in a new text file to start a new job. Then I do and update operation to extract the right 11 char's of a 13 char UPC code in order to link to a set based on the standard 11 char scan of a UPC code.
HEre's my problem. When I try to run the update operation to plop the 11 char UPC into it's field I get an error message stating that you can't update a field that's being used as a primary index. (the table has two indexes and this one is listed as the second one on the screen.)
My workaround so far has been to manually delete that index long enough to do the update, then manually define that index again so I can link to my set. Well, in the real world I have to find away around this that is pushbutton, not manual. (Dummy-proof.)
First, it's the second index defined for that table. How did it get to be the primary? Can I just set the other one to primary and if so, how?
If not, should I create a scripts that use the "index".drop and "index".add methods? Then maybe I could put a button on my Job Prep form that drops the index, runs the update, and then adds the index back? Is this the most efficient way? Any better ideas?
Any help is appreciated!
Chris Boullear
I have a table in an app that has to be zapped as we move from job to job. I then pull in a new text file to start a new job. Then I do and update operation to extract the right 11 char's of a 13 char UPC code in order to link to a set based on the standard 11 char scan of a UPC code.
HEre's my problem. When I try to run the update operation to plop the 11 char UPC into it's field I get an error message stating that you can't update a field that's being used as a primary index. (the table has two indexes and this one is listed as the second one on the screen.)
My workaround so far has been to manually delete that index long enough to do the update, then manually define that index again so I can link to my set. Well, in the real world I have to find away around this that is pushbutton, not manual. (Dummy-proof.)
First, it's the second index defined for that table. How did it get to be the primary? Can I just set the other one to primary and if so, how?
If not, should I create a scripts that use the "index".drop and "index".add methods? Then maybe I could put a button on my Job Prep form that drops the index, runs the update, and then adds the index back? Is this the most efficient way? Any better ideas?
Any help is appreciated!
Chris Boullear
Comment