SETFILE and COPY only work one direction? (AREV Specific)
At 25 APR 2000 10:08:00AM Michael Slack wrote:
I'm working with AREV 3.12. Recently I found that when I SETFILE from one application to another (both on the save server and under the save AREV system directory) that the COPY is only good in one direction. I found that if I copy rows from a table in the current application to a table in another application, the copy won't take (I even use the (A L O) options). But when I go to the other application (the receiving application) and use SETFILE and then COPY the rows into the current application, it works (still using the (A L O) options). Can anyone tell me why I can't seem to copy TO a table in another application but I can copy FROM a table in another application into a table in the current application? Is there something I'm missing in my attempts to copy from a table in the current application to another table in another application?
Thank You,
Michael Slack
At 25 APR 2000 01:54PM Steve Smith wrote:
Is one file GLOBAL account and the other tied to a different account?
What syntax are you using?
Steve
At 26 APR 2000 12:54AM Richard Hunt wrote:
This might help…
I have a table (file) called "SOURCE" in the "AWARE" application.
I use the command "SETALIAS AWARE\SOURCE AWARE SOURCE SOURCE"
This command will allow me to use the "SOURCE" table (file) that is in the "AWARE" application. I am able to "COPYROW" to and from this table (file).
At 26 APR 2000 09:39AM Michael Slack wrote:
Thank you for your help. Yes, one of the files is a global file. The one I wanted my row to go to is global but I referenced the wrong file. Resently one of our Database Administrators globalized several tables that a group of our applications had in common. The applications are identaical (or should be) except for the data. One application for each remote site. In globalizing the program (BP) table so the applications are truely using the same code, the DBA didn't clearout and/or remove the individual program table in each of the applications. So when I setfile, I setfile to the individual program table and not the global, but I looked in the gobal table for confirmation of a good copy. We'll have to clean this up so not to have this mistake happen again.
Thank You,
Michael Slack