Hi Al,

Thanks for taking the tiume to reply. I stumbled across the solution about a day after i put this message up. Because if the time difference here in Australia, I usually wait 1 day before looking for a reply!

Stupid me has some convoluted code actually setting the width to the different value for some other process when the lanscape mode was detected.

Regards...Rex

>The COPY FILE command should, in theory, create an exact copy of the file(s) you specify - much like the OS-level COPY command. A few things you could try:
>
>- run the FC command (at an MS-DOS prompt) to find out if the source and target files are truly identical
>
>- if they are not, and based on what you're seeing they probably aren't, a few other things to try:
>
>- ensure no one else has the file(s) open
>- open the .FRX as a table and use COPY TO
>- rather than COPY FILE xxx.*, try explicitly COPY FILE xxx.FRX followed by COPY FILE xxx.FRT. You might be copying temporary files that could be causing problems. I once had a problem with an old index file named .C01 causing problems with a .DBF/.CDX combination (at least the problems disappeared when I deleted it).
>- issue a FLUSH before the copy
>- might there be any network OS issues like Novell Client32 against a Novell server?
>
>>I use the VFP5 Report facility to output from my application. So that I can programatically set font, orientation, etc, I copy the created FRX and FRT files to a standard TEMP.FRX/FRT using
>>
>>cNewRpt = "TEMPRPT.*"
>>cOldRpt = cReport + ".*"
>>COPY FILE (cOldRpt) TO (cNewRpt)
>>
>>For most part this works, however, the 'width' column seems to end up with strange values when I copy a landscape mode report. All 'objtype' values of 6 (this is for a line) change to a value of 100100, even though they were originally various other values, such as 104.167, 25104.167 and 12604.167.
>>
>>In the past, I have checked for these values and changed them to what they should be, but can anyone tell me why it is happening and how to stop it from happening?