[Ed Borowski]

I am receiving the same error when I try to do a:

hcidbdump -e /p

[0:TEST] Unable to read msg data chain

but have no problem with the recovery database:

hcidbdump -r /p

Did you ever find out why this occured?

Thank you, Ed.

[Ed Borowski]

Thank you – that was exactly what I was looking for.  Clean, simple, and works great.

[Ed Borowski]

This is also for a result interface with CoPathPlus.  I’d like to think that there is a way to do it through tcl/grm/xpm, what I did for now is the following:

BULKCOPY

Check the first OBX, if no result text then PATHCOPY = to blank it out, then COPY fields from the first OBX segment, modify the one field I care about.  Otherwise leave it the way it is. (I don’t want to mess with it if it’s not in the format I’m looking for)

The reason for this is that our HIS (Quadramed Affinity) uses OBX(0)-3.1 as the text it displays in Results Access for what type of result your looking at, and CoPathPlus sends a unique identifier that isn’t descriptive.

Seems to work good.

Thanks, Ed.

[Author]

Replies