Portals and runtimes

[CommiC]

Hi, What I want to know is:

Is it possible to put a main database and the related portal database

in two seperate runtime modules?

CASE:

I have a db with 20 fields. 5 of them are stored in another db

connected as a portal.

I edit 15 fields weekly and send the database to the other person.

At his end he must be able to edit his db with 5 fields without using the main

database.

But when he starts the main database at his end, his 5 fields must showup in the portal window in the main db.

Hope it makes sence :-)

John

[CobaltSky]

Hello John,

What you are hoping to achieve is certainly feasible, but not by creating two separate runtime modules.

If the two files in question were bound separately to different runtime engines, the relationship would be broken. However binding them to the same runtime engine will not prevent you from opening the second file (the one with 5 fields) independently of the other - nor editing the main file and sending it separately as an update.

Moreover, when you send a revised copy of the main file (selecting it from among the files in the runtime solution folder at your end) and your colleague uses it to replace the corresponding file in the runtime folder on his/her system, then the next time the runtime is launched it will hold the updated main file information.

[CommiC]

This setup works, thanks Ray!

[BuddySystems]

Actually, I believe as long as the runtime solution has the same name and same binding key and you always use files with the same names, it will work, even if they are bound at different times.