|
> - Are you upset w/ the direction IBM has taken regarding DDS vs. SQL? What I think is missing is a decent way to maintain a dictionary. I.e. define a field in one place and not in every file that contains it. Once there was IDDU, but it was unworkable and seems to have sort of faded away. Because of that we use our homegrown dictionary tool which currently generates DDS. But it would not be that difficult to change to SQL. What is keeping away from SQL for now is the default editing in SQL; no defining of edit codes or edit words. > - Do you need more than one file defined in CLP? No. > - Do you need to be able to update files within CLP? No. > - Are you fighting w/ embedded SQL, due to precompiler restrictions? No. We hardly use it. What I do miss in CL (and DDS; especially for printer files) is the ability to define compile options in the source. Joep Beckeringh
As an Amazon Associate we earn from qualifying purchases.
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.