RE: Advice needed on a multimember DDS file to be converted to DDL

[<lgoodbar@xxxxxxxxxxxxxx>]

Jeff,

If you are wholly moving the orders from the old "member" to the new,
then yes that would be sufficient. Keeping an index on the member field
would make it a quick process.

Loyd Goodbar
Business Systems
BorgWarner Shared Services
662-473-5713

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Friday, April 25, 2008 1:44 PM
To: Midrange Systems Technical Discussion
Subject: Re: Advice needed on a multimember DDS file to be converted to
DDL

Agreed on the changing MEMBER field.  I envisioned that program 
utilizing an SQL statement like

update <file> set member = <newmembername> where member =
<oldmembername>

lgoodbar@xxxxxxxxxxxxxx wrote:
> If you added the MEMBER field as you suggest, then the CL overrides,
> instead of being to MBR(), simply restrict to MEMBER=something. You
> would need to recompile the RPG programs due to the added field, but
if
> they don't "do anything" with members today, why would they tomorrow?
>
> How do orders go from one member to another? Now THAT program would
have
> the biggest change.
>
> No real reason to use SQL here, although you can do something like
> With temp as (select fields from orhdr where member=blah) etc.
> ...which effectively performs the same task as OVRDBF.
>
> Loyd Goodbar
> Business Systems
> BorgWarner Shared Services
> 662-473-5713