Ok,
Some are saying that you can use them with aliases, etc. and I assume you
just said that won't work Jeff.....I'm confused.
From: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 08/15/2008 03:36 PM
Subject: Re: DDL Files - Tables and keys
----------------------------------------------------------------------
Now who would do that?
Oh wait - I DID!
--
Jeff Crosby
UniPro Foodservice/Dilgard
260-422-7531
Opinions expressed are my own and not necessarily those of my company.
Unless I say so.
vhamberg@xxxxxxxxxxx wrote:
> Doug
>
> SQL does not process multiple-member files at all. So if you go the DDL
route, you can't use them.
>
> The usual way to do the same kind of thing is to add a field that could
be, say, the member name in the multiple member file - and use that as
part of a where clause.
>
> HTH
> Vern
>
> -------------- Original message --------------
> From: Doug Palme <DPalme@xxxxxxxxxxx>
>
>
>> Boy you are really going to get me into trouble here......this outfit
uses
>> multiple member files like there is no tomorrow.....
>>
>> Can you explain why no multiple members? I need some explanation
because
>> I will be asked.
>>
>> From: rob@xxxxxxxxx
>> To: Midrange Systems Technical Discussion
>> Date: 08/14/2008 04:43 PM
>> Subject: RE: DDL Files - Tables and keys
>>
>> ----------------------------------------------------------------------
>>
>> Oh,
>> - No multiple members.
>>
>> Rob Berendt
>> --
>> Group Dekko Services, LLC
>> Dept 01.073
>> Dock 108
>> 6928N 400E
>> Kendallville, IN 46755
>>
http://www.dekko.com
>>
>> "Wilt, Charles"
>> Sent by: midrange-l-bounces@xxxxxxxxxxxx
>> 08/14/2008 02:16 PM
>> Please respond to
>> Midrange Systems Technical Discussion
>>
>> To
>> "Midrange Systems Technical Discussion"
>> cc
>>
>> Subject
>> RE: DDL Files - Tables and keys
>>
>> Always use a primary key...
>>
>> SQL standards recommend it.
>>
>> You can't use FK constraints without it...
>>
>> You can't even use CPYF MBROPT(*UPDADD)....
>>
>>
>>
>> Charles Wilt
>> --
>> Software Engineer
>> CINTAS Corporation - IT 92B
>> 513.701.1307
>>
>> wiltc@xxxxxxxxxx
>>
>>
>>> -----Original Message-----
>>> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
>>> bounces@xxxxxxxxxxxx] On Behalf Of Doug Palme
>>> Sent: Thursday, August 14, 2008 1:47 PM
>>> To: Midrange Systems Technical Discussion
>>> Subject: DDL Files - Tables and keys
>>>
>>> There is going to be a standards meeting tomorrow and I have been
>>> writing
>>> up some notes and suggestions for DDL files. Any additional Input
>>>
>> from
>>
>>> the group would be appreciated.
>>>
>>> One thing I was going to suggest was that tables should be created
>>> without
>>> any keys, unless there is a specific reason to use a PRIMARY key,
>>>
>> which
>>
>>> I
>>> believe is the only key you can add to a table....correct? We should
>>> use
>>> Indexes for keyed data and views for those files that we need
>>>
>> specific
>>
>>> fields displayed or criteria applied.
>>>
>>> Any other suggestions as it relates specific to Tables and keys?
>>> This transmission may contain information that is privileged,
>>> confidential
>>> and/or exempt from disclosure under applicable law. If you are not
>>>
>> the
>>
>>> intended recipient, you are hereby notified that any disclosure,
>>> copying,
>>> distribution, or use of the information contained herein (including
>>>
>> any
>>
>>> reliance thereon) is STRICTLY PROHIBITED. If you received this
>>> transmission in error, please immediately contact the sender and
>>> destroy
>>> the material in its entirety, whether in electronic or hard copy
>>> format.
>>> Thank you.
>>> --
>>> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
>>> list
>>> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
>>> To subscribe, unsubscribe, or change list options,
>>> visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
>>> or email: MIDRANGE-L-request@xxxxxxxxxxxx
>>> Before posting, please take a moment to review the archives
>>> at
http://archive.midrange.com/midrange-l.
>>>
>>>
>> This e-mail transmission contains information that is intended to be
>> confidential and privileged. If you receive this e-mail and you are not
a
>> named addressee you are hereby notified that you are not authorized to
>> read, print, retain, copy or disseminate this communication without the
>> consent of the sender and that doing so is prohibited and may be
unlawful.
>> Please reply to the message immediately by informing the sender that
the
>> message was misdirected. After replying, please delete and otherwise
>> erase it and any attachments from your computer system. Your assistance
>> in correcting this error is appreciated.
>> --
>> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
>> list
>> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
>> To subscribe, unsubscribe, or change list options,
>> visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
>> or email: MIDRANGE-L-request@xxxxxxxxxxxx
>> Before posting, please take a moment to review the archives
>> at
http://archive.midrange.com/midrange-l.
>>
>> --
>> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
>> list
>> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
>> To subscribe, unsubscribe, or change list options,
>> visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
>> or email: MIDRANGE-L-request@xxxxxxxxxxxx
>> Before posting, please take a moment to review the archives
>> at
http://archive.midrange.com/midrange-l.
>>
>> This transmission may contain information that is privileged,
confidential
>> and/or exempt from disclosure under applicable law. If you are not the
>> intended recipient, you are hereby notified that any disclosure,
copying,
>> distribution, or use of the information contained herein (including any
>> reliance thereon) is STRICTLY PROHIBITED. If you received this
>> transmission in error, please immediately contact the sender and
destroy
>> the material in its entirety, whether in electronic or hard copy
format.
>> Thank you.
>> --
>> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
>> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
>> To subscribe, unsubscribe, or change list options,
>> visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
>> or email: MIDRANGE-L-request@xxxxxxxxxxxx
>> Before posting, please take a moment to review the archives
>> at
http://archive.midrange.com/midrange-l.
>>
>>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
This transmission may contain information that is privileged, confidential
and/or exempt from disclosure under applicable law. If you are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution, or use of the information contained herein (including any
reliance thereon) is STRICTLY PROHIBITED. If you received this
transmission in error, please immediately contact the sender and destroy
the material in its entirety, whether in electronic or hard copy format.
Thank you.
midrange.com
