ldc@cbnewsm.ATT.COM (derrick.j.mitchell) (01/08/90)
First I must say thanks to the answers to my previous question. My other problem is the followings: USE parts SET INDEX TO parts SELECT 0 && Get the next available work space USE supplier SET INDEX TO supplier SELECT 0 USE custpart SET INDEX TO custpart SET RELATION TO part_no INTO parts, id INTO supplier When I compile the above using "Clipper Sum/87" I get a "SET RELATION error". From what I read in the manuals the above should work. The data file "parts" is INDEXed on part_no. Also, the data file "supplier" is INDEXed on id. If I try splitting it into two SET RELATION there is no error. SET RELATION part_no INTO parts SET RELATION id INTO suplier However, the last SET RELATION canceled the previous one, as expected. If after splitting the command I add the ADDITIVE option to the Clipper compiler flags an error and ignore the ADDITIVE SET RELATION part_no INTO parts ADDITIVE SET RELATION id INTO suplier ADDITIVE It is now sunday evening...... I give up. Again Thanks in advance for you help.
nfs0294@dsac.dla.mil (Glendell R. Midkiff) (01/08/90)
From article <8328@cbnewsm.ATT.COM>, by ldc@cbnewsm.ATT.COM (derrick.j.mitchell): > SET INDEX TO custpart > SET RELATION TO part_no INTO parts, id INTO supplier > When I compile the above using "Clipper Sum/87" I get a > "SET RELATION error". I had the same problem when I first started using the SET RELATION Command. Try splitting the line and use a ';' at the end of the first line: SET RELATION TO part_no INTO parts,; TO id INTO supplier See the example on page 5-182 of the manual. -- |-----------------------------------------------------------------------| |Glen Midkiff osu-cis!dsacg1!gmidkiff | |From the Internet: gmidkiff@dsac.dla.mil | |Phone: (614)-238-9643 @DLA, Systems Automation Center, Columbus, Oh. |