On 26-Oct-2011 12:02 , Paul Nelson wrote:
The PRTMSTID field seems to point to the PRTMST file. Same goes for
the SYTCNC file.

Rewriting an application just to say you use SQL seems to be penny
wise and pound foolish. I know there are other clients of this vendor
who have embedded CPYF statements in some of their custom CLP's that
are going to be cranky at having them break just because of this.

If the presumed-as or alluded possible issues with CPYF are meant to imply some specific relationship to Foreign Key constraints, then please realize that the issue is not specific to the SQL. Either ADDPFCST TYPE(*REFCST) or ALTER TABLE ADD CONSTRAINT FOREIGN KEY is [with necessary attributes established; e.g. MAXMBRS(1)] still valid for DDS-PF, just as for SQL TABLE.

How CPYF is utilized must be understood within the context of the database file definitions and means of data manipulation irrespective of DDS or SQL DDL as the definition\description language.

In other words, no matter what definitional language, if CPYF is used without proper understanding of the database and how the database is being manipulated, the use of CPYF may be problematic. But the same could be said about using SQL or RPG without the same level of understanding about the database; i.e. if you do not know what you are doing, do not mess with it :-)

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.