This sounds like a problem that was discovered in SARscape 5.0 and fixed in 5.0 SP1 (5.0.1). If you update your SARscape with the first service pack to SARscape 5.0, then that should resolve this problem. If you are already running that version of SARscape, then it would probably be most efficient for you to submit this question to Exelis VIS Tech Support or your local distributor, so they can track down the problem for you.
- Peg
Exelis VIS Technical Support
|