T
tbarring
Guest
1. Store the payload: Absolutely. 2. Ummm... maybe not necessary. If you don't have EDC you can still get the messages via a server call and then deal with storing them yourself. Alternatively, the messages could be streamed to a flat file or .csv. 3. Ideally you should be able to either create the table or assign this functionality to a pre-existing table with (some superset of) the right structure. 4. Phase II. 
But this does point up a limitation of Corticon vis-a-vis OpenEdge: OE clients don't care what DB their data comes from; it's invisible to the code. I can do a join between two tables in different DBs. But a Corticon vocabulary must all be in one DB. Perhaps if that changes, this option becomes more reasonable...
Continue reading...
But this does point up a limitation of Corticon vis-a-vis OpenEdge: OE clients don't care what DB their data comes from; it's invisible to the code. I can do a join between two tables in different DBs. But a Corticon vocabulary must all be in one DB. Perhaps if that changes, this option becomes more reasonable...Continue reading...