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 04 MAR 2003 04:11:57PM Martin Bell wrote:

ARev 3.12, Novell 4.1 w/NLM, Win98 client

A letter processing function uses MERGE with various merge documents to generate letters from a customer file. It runs daily, generally without incident.

Sometimes, a particular merge document, 1.FWD, occurs in the run for perhaps 10 customers and the letter process completes normally. Other times, it will hang while showing the normal message that the MERGE is being performed.

So here's what I know so far:

1) It doesn't always hang when a 1.FWD occurs

1B) ANY hang is always a 1.FWD.

1C) A hang can not be broken, period.

2) It doesn't consistently hang on the same source record when a 1.FWD merge occurs – that is, once it does hang, subsequent re-runs using the same customer data and merge document (1.FWD) don't necessarily hang.

3) I added a quick audit log just prior and subsequent to the MERGE execution, and I can confirm that the hang is definitely within the confines of the MERGE call.

4) I've recreated the 1.FWD merge document, think that there might be some sort of corruption, but I still get the same results as before.

5) The output is to a network printer, so I'm considering holding the print que and seeing if there's any difference. Yet this idea doesn't make much sense in that it is always a 1.FWD that causes the hang.

Any suggestions would be greatly appreciated.


At 05 MAR 2003 03:19PM Curt Putnam wrote:

Suggest reviewing the integrity of all files and indexes used by the merge. Sounds as though there is a bad index node or a GFE somewhere.

View this thread on the forum...

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