Client Access .dtf differences -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Client Access .dtf differences
From: "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>
Date: Thu, 10 Apr 2008 08:31:28 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I have two .dtf transfer requests running off of one PC. This is an automated procedure which runs a query on the i5, then runs the .dtf to create an Excel file on the PC drive.

One of the two dtfs works fine set up as a scheduled job. There is no intervention needed. However, the 2nd dtf pops up the Client Access screen for the Transfer (the dtf) and forces a click to run it.

I can't imagine what is different between the two jobs??

TIA,
Don

Don F. Cavaiani
IT Manager
Amerequip Corp.
920-894-7063

"It's amazing what you can accomplish if you don't care who gets the credit." Harry S. Truman

Follow-Ups:

RE: Client Access .dtf differences , Don Cavaiani

This mailing list archive is Copyright 1997-2026 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.