RE: Question About DDMF

Marvin,

The only thing I can think of is a trigger program that quietly throws
away updates from DDM.

However, IMHO you'd be better off dumping the DDM file altogether.
Having DDMF between production and development is a very poor idea as
you've found out the hard way.  I consider DDM between production and
development the lazy way of making sure development has updated data to
work with.  The downside is that it limits the testing you can do in
development.  If you can't test programs that make updates to files, why
bother testing at all?  

Ditch the DDM and simply restore the production library to development
on a regular or as needed basis.

HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Marvin Radding
> Sent: Tuesday, May 09, 2006 11:21 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Question About DDMF
> 
> 
> We are having a problem with programs on our development 
> machine updating our production environment through a DDMF.  
> Is there a way to limit DDMF to read only on the Production 
> machine? Or a way to limit DDMF on the development machine to 
> read only? Gotta stop updating through DDMF.
> 
> Marvin
> 
> -- 
> 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.
> 
>