RE: QTEMP was: Creating a physical AND Logical file

I don't think I've ever seen this done. AFAIK we have NEVER duplicated a
file into QTEMP for the purpose of using it AND the production file that
was duplicated. I'm sure there must be a reason to do this since you and
Alan appear to be doing it. 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, January 12, 2007 10:04 AM
To: Midrange Systems Technical Discussion
Subject: QTEMP was: Creating a physical AND Logical file

If you
1 - Name the qtemp file the same name as the production file
2 - and put qtemp at the top of your library list it must be a real
trick to get the OVRDBF right to read both the qtemp, and the production
version, in the same program.

However if you put qtemp at the end of the library list it becomes quite
easy to simply put one OVRDBF in there for OVRDBF XYZqt
TOFILE(QTEMP/XYZ)

Now your application software may have tricks like a data area that
stores the name of the production library and you can read that and
apply that in your OVRDBF but when you have a mishmash of vendor
software it becomes a hoot.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
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.