Skip to main content

How do I force a RunTime Error to test for RC=32 (NX 5.1 WP6)

  • June 28, 2013
  • 2 replies
  • 2 views

I have added code to trap Runtime Errors like RC=32 but not sure how i can trap this during a test. I have an IDX file that is being read but once the program starts it locks the file so I cannot move it during execution as a test.

(NX 5.1 WP6)

 

2 replies

Chris Glazier
Forum|alt.badge.img+3

I have added code to trap Runtime Errors like RC=32 but not sure how i can trap this during a test. I have an IDX file that is being read but once the program starts it locks the file so I cannot move it during execution as a test.

(NX 5.1 WP6)

 

Can you please provide more detail as to what is the exact condition that you are attempting to trap here? Is it a file not found condition, etc.?

Thanks.


  • July 31, 2013

I have added code to trap Runtime Errors like RC=32 but not sure how i can trap this during a test. I have an IDX file that is being read but once the program starts it locks the file so I cannot move it during execution as a test.

(NX 5.1 WP6)

 

We have a client who is seeing RC=32 in the command window of their Win 7 desktop. I am attempting to replicate that - appears that RC is associated to multiple open indexed files. Our application is opening just one indexed file so not sure why the RC32. It also appears that Hyperthreading may have something to do with this. We have requested them to turn off Hyperthreading but they do see this error now although occassionally - before turning it off, it happened with every run of the application. I am just trying to replicate their issue in-house, to decide on the resolution.