Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 06 FEB 2002 07:40:28PM F Dietrich wrote:

Hi,

I recently made a patch with the RDK that is supposed to install a table I've modified. I put the table into the repository view and selected Deploy next to it in the Deployment Definition. Now when I run the RDK on a runtime version, I see two versions of the same table. In other words, if I go into the System Editor and say Open Record, I see two identical entries in the Table list. If I go into the Database Manager, I see two entries also. If I look up the table in LH Table Info in the Database Manager, I not only see two entries, but the data on them is totally identical. Worst of all, the runtime version is still bringing up the old data.


At 06 FEB 2002 08:21PM Donald Bakke wrote:

I've not seen this problem before, but then again I haven't attempted to use the RDK to deploy whole tables either. This sounds like the application's DBT file has an extra entry in it. I would manually modify its contents (AREV is the best tool for that) or try to remove the table references with the Database Manager and then re-add the table and save the configuration.

I also doubt that the new table ever deployed. Even though the RDK seems to have added a table reference it would appear that the actual table was not deployed or it was deployed and the media map wasn't updated.

We have been manually moving our table/dictionary tables over (unless we are only updating a few dictionary columns, in which case we do use the RDK.) You could create a repository entry for Operating System Files which this table as long as the DOS names are the same. It should simply overwrite the existing files with the ones you are deploying.

[email protected]

SRP Computer Solutions, Inc.


At 06 FEB 2002 09:55PM Robert Lee wrote:

Likewise, I haven't used RDK to deploy a table - at least not the new functionality allowed in 3.7.5.

However, when you deploy an application with RDK, it creates a standard LH arrangement with Revmedia.lk & Revmedia.ov files. This means you can copy (using COPYTABLE) a table of your choice to the RDK upgrade folder.

The second part of the problem is to install the new table / records when the RDK Upgrade is installed. The best way to accomplish this is make your program which calls RDKINSTALL also call an "Upgrade Maintenance" program immediately after the call to RDKINSTALL. This program will have arrived on the upgrade and can do whatever housework you require including copying / deleting tables and records, and displaying upgrade notes etc.

This maintenance program would first have to attach (ATTACH_TABLE) to the upgrade folder after which you could call COPY_TABLE, DELETE_TABLE, COPY_ROW etc., with the priviso that the name of the table in the upgrade has a different name from the live table on the clients system.

Hope that makes sense. Its easier than it sounds.

Robert Lee


At 07 FEB 2002 08:06AM Richard Bright wrote:

Robert,

All this copy table stuff is built into RDKINSTALL. Take some time out to spin thru the subroutine that RDKINSTALL calls - RDKMODULEINSTALL. There you will find that you can do all sorts of things. Many of the processes can be defined in the SYSUPGRADE record PROCESS under headings such as COPYTABLE and ATTATCH_TABLES. The RDKMODULEINSTALL gives the syntax.

See SYSPROCS, RDK_DEPLOY EQUATES ie

EQU CREATEFILE$ TO"CREATE TABLES"

EQU COPYFILE$ TO "COPY TABLES"

EQU DELETEFILE$ TO "DELETE TABLES"

EQU ATTACHFILE$ TO "ATTACH TABLES"

EQU DETACHFILE$ TO "DETACH TABLES"

EQU ALIASFILE$ TO "ALIAS TABLES"

EQU COPYOSFILE$ TO "COPY OSFILE"

EQU UPDATEROW$ TO "UPDATE ROWS"

EQU DELETEROW$ TO "DELETE ROWS"

EQU EXECPROC$ TO "EXECUTE PROCEDURES"

EQU LINKPROCESS$ TO "CHAIN PROCESS"

EQU DECLAREDLL$ TO "DECLARE DLL"

One of the things I did once was to load in a SSP, run it to do some houskeeping, then remove it from the system. The key is that RDKINSTALL gets the stuff to be registered in the Repository.

Richard Bright

BrightIdeas New Zealand

[email protected]


At 11 FEB 2002 06:00PM Robert Lee wrote:

Hi Richard

Hmmm. Interesting. Tell me more. After the upgrade has been deployed, I presume you attach to the upgrade, and update the %PROCESS% record, either with a program you have written or with the system editor. Did I miss some docs on this or is it a matter as you suggest of reading the program code?

Robert Lee

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/f44d55b25d5531bb88256b590003b476.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1