|
Eric, You're the man! I will readily admit that I'm an SQL dummy. So I have to ask, how does this translate into a creatable, maintainable source member? For example, I have a field AccountNumber which is used in 14 different physical files. Each occurrence needs to have a different name to avoid buffer to variable content conflict. I.E. AccountNumber in master file vs AccountNumber in transaction file. Some languages, not RPG, will prefix the variable by the file name, but we live in an RPG world. So please educate me on how I can extrapolate AccountNumber to 14 uses, uniquely named? "Eric N. Wilson" wrote: > > > What about the Domain keyword that most every SQL implementation I know of > other than DB2 UDB supports? Then you can say that this field is a > AccountNumber field and it would take on the attributes of the Domain > AccountNumber. > > The syntax for the command is > > Create Domain AccountNumber as Integer > > Or you could be more creative and add check constraints to the domain > > Create Domain AccountNumber as Integer > Check((Value >= 100) Or Value Is Null) > > Then you will have the Handy Dandy AccountNumber DataType available for your > SQL enjoyment :-) > > ______________________________________________ > Eric N. Wilson > President > Doulos Software & Computer Services > 2913 N Alder St. > Tacoma WA 98407 > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.