[[https://www.revelation.com/|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]]
==== Respistory (OpenInsight 32-bit Specific) ====
=== At 16 JAN 2003 01:33:13PM Jeff Miller wrote: ===
{{tag>"OpenInsight 32-bit Specific"}}
I have a unique situation. I have runtime system running that my client uses to run the OI application. I have on a stand alone machine put a development version of OI. I have attached the runtime's tables including the stored procedures and forms. So I can make a change the program via the development version and the runtime system will reflect the change at the time I change. In other words I do not go thru updating an RDK to get the changes. This has been working well with the exception of new stored procedures and forms. Even though they have been saved in their proper tables the system cannot see them. My guess it the system has not made an entry in the repository.
Does anyone know how to update the proper files/repository so that I do not have to kick everyone off or wait until the end of the day to complete the process?
Or does anyone have a better idea?
The last time I made the request for everyone to get off you would have thought I asked some of them to take a flying leap.
Thanks
Jeff
----
=== At 16 JAN 2003 02:18PM Donald Bakke wrote: ===
Jeff,
Using the Check-Out tool is probably the best way to accomplish this. You'll use your own system files but you can transfer development components without having to log them off (unlike the RDK).
Otherwise, you'll have to figure out a way to attach their repository and copy those records manually as well.
dbakke@srpcs.com
[url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]
[img]http://www.srpcs.com/srpicon1.gif[/img]
----
=== At 16 JAN 2003 09:37PM Jeff Miller wrote: ===
Don
How do you use the check out tools in a runtime. I have not spent much time looking for this function in a runtime. Will it be a program like the update of an RDK, where you have a program around the update function?
----
=== At 16 JAN 2003 11:32PM Donald Bakke wrote: ===
Jeff,
You don't have to involve the runtime system. The check-out tool can be used in two ways:
1. Use the source (i.e. development) system to check-out/copy-to into an empty folder. Then use the destination system to check-out/copy-from this folder where the files were placed. Using it in this fashion is similar to how the RDK is used. It's a two-step process.
2. Use the source system to check-out/copy-to directly into another, i.e. destination, system. Hence, this is a one-step process and doesn't require you to run anything on the runtime.
Therefore I am suggesting you use option #2. The requirement is that your development system must see the runtime system. Another advantage of the check-out tool is that it utilizes the repository so you can select one component and then drill down and select components that are related to it (i.e. a window, its events, and images.)
The limitations of the check-out tool are: 1.) You can't save your check-out "image" like you can with the RDK, and 2.) you can't do advanced things like create tables, create indexes, create applications, run stored procedures, etc.
Each tool has its strengths and weaknesses. Which is fine as long as you understand them both.
dbakke@srpcs.com
[url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]
[img]http://www.srpcs.com/srpicon1.gif[/img]
----
=== At 17 JAN 2003 12:10AM Ray Chan wrote: ===
Jeff,
[i]Or does anyone have a better idea?[/i]
You may want to take a look at Sprezzatura website. Under S/ENL, vol 2, Issue 6, I believe that you may find an article that may help you, at least I hope so.
Good luck.
Ray Chan
----
=== At 17 JAN 2003 02:14AM Donald Bakke wrote: ===
Ray,
I think the problem will be that he is running the development system on a local machine and not the network. Possibly he has this on a laptop (in order to take the work away) so that article won't help in this situation.
dbakke@srpcs.com
[url=http://www.srpcs.com]SRP Computer Solutions, Inc.[/url]
[img]http://www.srpcs.com/srpicon1.gif[/img]
----
=== At 17 JAN 2003 09:02AM Richard Guise wrote: ===
For what it's worth ...
We use "dynamic attaching" (to coin a phrase) quite a lot - as when the database changed (esp indexes & MFSs) we had quite a few problems with the DBT files.
However, files like SYSPROCS, SYSOBJ, the SYSWINs, etc. are not going to change. Hence leave them in the DBT to attach automatically every time.
For the database files take them out of the DBT file (either via OI or manually) and run a procedure at logon to attach them (dynamically). Thus all the files are there, the indexes, MFSs, etc. - no problem.
However, to use screen painter, etc. it's then necessary first to run the application including the logon routine to attach the files. Then exit and go straight to open the app and use the development tools.
However, if you use the RDK to update the remote site, many of the commands include a call to update the DBT to match current database configuration. Hence remote site goes back to square one. Therefore doctor RDKMODULEINSTALL to remove the DBT updating calls (or make them an extra option). Tweaking RDKMODULEINSTALL is another large subject!
By the way ... We also wanted to run an application to be switchable between several similar but individually configured databases. The logon routine therefore asks which database and then attaches the chosen one. A main menu screen button offers database switch, detaching the current one and attaching the newly selected one. It's very quick and convenient.
Hope some of this helps
Richard Guise
Tornado Property Systems Ltd.
----
=== At 01 FEB 2003 07:35AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote: ===
Depends on what you want to do. By attaching their SYSTEM files, you are effectively running a devlepment copy on THEIR system, so what you end up with is changes made will then not be reflected on YOUR system.
So, depending on what you want to accomplish, their are various methods to do this.
If that is what you wish, then the SENL article is the correct method, sicne it will give access to their runtime system using your development engine. Any changes made will only be made in their system, including new repository entities. When you disconnect and go home, you'll find you don't see those changes.
If you want to have the source changes on your system, then you will either need to use the Checkout functions or the RDK.
[url=http://www.sprezzatura.com]The Sprezzatura Group[/url]
[i]World Leaders in all Things RevSoft[/i]
[img]http://www.sprezzatura.com/zz.gif[/img]
[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=E8F6F2934794926585256CB00065EB1B|View this thread on the forum...]]