|
DDM does not not care where or how a file is updated. It's only purpose in life is to "point" where the file in question is physically located. The program opening the file doesn't know or care where the file is located. Bad system design using DDM files will create a LOT of system overhead that can not be fixed. A program running on development machine updating a file on the production machine "might" or "might not" create heavy traffic. That depends on (1) Line speed (2) number of updates If you are attempting to read and write thousands or millions of records on every update, the overhead will be incredible. Marvin Radding wrote:
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 toread only on the Production machine? Or a way to limit DDMF on the development
machine to read only? Gotta stop updating through DDMF.
Marvin
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.