I am running AREV 2.1 on two pc's. One is a "TEST" System on one pc the other is in a Production Environment (Server 2000).

How can I move my test Window Templates and Basic Programs from my "Test" pc to my Production Server. My Test PC is in one not in the same building as my production server.

Thank you

I work in AREV 3.12 so the instructions won't be precise. The thing to remember is that what you are talking about are rows in tables.

The simplest thing to do is to copy the rows to a DOS file. Some how transport those files to your production machine. There copy the DOS files into your table(s). Remember that DOS has the file name limitation of 8.3. So you'll most likely have to name your DOS files going out and rename them as they go into your production environment.

Once the source code for the programs are in your production, you'll need to recompile and create a VOC listing (I assume using SETPROGRAM). Or with a little more work, you can also copy the four parts of the program to DOS and then into production. The four parts would be the source code, object code (program name starting with '$'), the variable transalation row (program name starting with '*') and the VOC entry (created by SETPROGRAM).

To help do this coping, you should have either a TCL COPY or COPYROW command. They are the same command. The COPY command brings up a copy window to help guide you thru building the command. So you should be able to copy several rows from a given table at one time. When you hit F9 to run the copy, it'll actually create a TCL command that you can look at later.

What I would suggest to do in is to copy the TCL COPY command to Notepad so you can manipulate it later to create the COPY command to copy the DOS files into production. Assuming everything is called the same thing. Especially if it's a long command. I don't trust my typing. I'm assuming that you'll copy and paste into the production side TCL command. If you want to create the production side COPY command from scratch, having the copy command in a Notepad document to refer to is a help.

If you copy from development a row in a Table to a DOS file and then from DOS file to a row in a table in production, you won't need to convert to DOS format and back to Revelation format.

So it might go something like this.

Development:

At TCL: COPYROW (TABLENAME) (ROWNAME) TO:(DOS C:\(DOS FILE NAME)

This is assuming that you are coping to the root of your C: drive.

Thru windows copy (DOS FILE NAME) to a thumb drive. If you wish, you can copy directly to your thumb drive. Or however you get the DOS files to your production machine.

Production:

Just reverse the process above.

Copy DOS file from thumb drive to root of C: (or where ever).

At TCL: COPYROW DOS C:\(DOS FILE NAME) TO:((TABLENAME) (ROWNAME)

You are essentially done at this point. Of course there may be other things you need to do, like compiling programs and whatnot.

Remember that you can copy several rows from a single table in one copy command. For example:

COPYROW (TABLENAME) (ROW1) (ROW2) (ROW3) TO:(DOS C:\(DOS FILE NAME1) C:\(DOS FILE NAME2) C:\(DOS FILE NAME3)

You always need to be cautious whenever you do something like this. This same process can be used on other tables. Like data tables, dictionary tables, the popup table, the menu table and so on. You need to be careful every step of the way.

I hope this helps.

Michael Slack

ARev 2.1 uses the COPY command, not COPYROW but it has the same syntax.

You may need the overwrite option "(o" if the records exist in target files already. Be sure to backup the old records of files.

If the production version is runtime only you will have to copy over the object code and optionally the symbol tables for the programs. Preface the program name with a dollar sign for object and an asterisk for symbol tables.

You could just write an RBasic program to write the records to and from temp files that you either put on removable media, copy across the lan/wan or email to yourself.

Thanks Guys. Both of your solutions worked. The only thing left is how do I copy the Dictionary. I got the windows template over fine.

Paul

Thanks Guys. Both of your solutions worked. The only thing left is how do I copy the Dictionary. I got the windows template over fine.

Paul

Hello Paul:

Dictionaries are just tables like everything else. So the same methods you used to get the programs and windows moved will work for dictionary rows. A word of warning, you probably don't want to copy all dictionary rows in mass because there are some system rows that deal with the particular data and other internal goings on. I would suggest that you stick to the real fields, symbolics and groups that were created by you or somebody else. I would recommend that you leave alone any dictionary rows with a name starting with "%" or "@".

So instead of a table name like "WINDOWS", you would use DICT.(tablename) in your copy command.

Mr. Auyong gave very good advice about backups and so on. The same goes for dictionary rows as well.

Michael Slack

Thanks Michael. I will start the copy and see how it goes. So far the windows entry screens went well.

Thank you

View this thread on the forum...