×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Sorry. I wasn't thinking about the users actually using that object on
the backup machine.
First, I would contact Lakeview support and run this by them.
You're kind of talking about 2-way replication. You want the changes from
the upgrade replicated from A to B. You want the changes to the data by
production occurring replicated from B to A.
Not totally out of the realm of possibility. I work in Domino and we do
this all the time. It replicates format changes on the fly. You can
change column X on row 27 on server A and column Y on the same row on
server B and it would get them in sync. Now, if both A and B changed
column X in between syncs you would end up with a "Replication or save
conflict" and I've seen my fair share of them. "Interactively" I've even
been warned "someone changed that document while you were working on it,
do you want to save it as a replication or save conflict?".
I tried to talk common lingo. Domino is not a relational DB system and
doesn't use terms like Row (that's a document) or Column. And doesn't
support a sql syntax to their documents. Not to say that you can't imbed
sql in their NSF's to go get SQL data from other systems (like DB2 on IBM
i). We do that all the time.
Rob Berendt
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
