RE: QTEMP was: Creating a physical AND Logical file

 <snip>
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)
</snip>

It is equally as easy to:
OVRDBF XYZpr TOFILE(PROD/XYZ)
;-)


Thanks,
Tommy Holden


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