DIAdem

cancel
Showing results for 
Search instead for 
Did you mean: 

Why does my script end at "PicLoad(PicFile)"?

It got a bit better!
Now it's 1 of 3 times it strikes...
Actually I'm not really wanting to put my whole tdr online "for everybody" - can I mail it to someone?

I reduced my tdr to one sheet (which I only used) for upload, but with that one worked so far everytime with the script, without mistake.
I'll reduce my template and see if that helps, too.
0 Kudos
Message 11 of 17
(1,908 Views)

Hi Yeti,

Feel free to email your TDR to brad.turpin@ni.com.  DIAdem R&D has agreed to take a look at it and see if they can figure out the issue for us.

Brad Turpin
DIAdem Product Support Engineer
National Instruments

0 Kudos
Message 12 of 17
(1,893 Views)

Hello I know this message has been out there a while but I would like to know if a solution was ever found.  I am having a similar issue that I need to get rid of. 

 

Thanks,

 

Eli_A

0 Kudos
Message 13 of 17
(1,412 Views)

Hi Eli_A,

 

I don't remember how this issue ended-- it was over 3 years ago.  It helped with the previous customer for him to post/send his error log file-- would you please do the same?

 

Brad Turpin

DIAdem Product Support Engineer

National Instruments

0 Kudos
Message 14 of 17
(1,400 Views)

Hi Brad,

 

Below you will find the pertinent content of the error file:

 

296  10:17:59 AM Error:
     Error while executing "PicLoad" command
     Error type: ACCESS VIOLATION
     Error address: 0000F1B3
     Module name:ntdll.dll

 

The curious thing is when I run my application which includes this script for the first time with a unit that passes I receive this error.  If I turn around and run the application again everything runs well, no errors.  I find that if I call the application for the first time with a unit that fails it works every time.  If I load the form manually and run a unit that passes I do not get the error and it works.

 

Here is another monkey wrench.  If I open the environment and load all the data into the channel groups and run the script using the debug/continue script button without any breakpoints it works correctly,  but if I open the environment and load all the data into the channel groups and run the script using the run script button it doesn't work.  Is there a difference between the two ways of running the script that may be helping or hurting?

 

Elias

0 Kudos
Message 15 of 17
(1,390 Views)

Hi Eli_A,

 

I do not understand what is going on, but let me recommend that you try adding this command before any other REPORT commands in your script:

 

Call WndShow("REPORT", "OPEN")

 

Let me know if that helps,

Brad Turpin

DIAdem Product Support Engineer

National Instruments

Message 16 of 17
(1,383 Views)

Hi Brad,

First I want to thank you for your help.  Your suggestion proved valuable.  I took the code you suggested and place it above the “PicLoad” command.  It did not work, but I decided to use it as a tool.  I started moving it up my code until it worked hoping this would point to the sub-routine that was causing the problem and it did.  At one point it started to work.  I then looked into that subroutine and what I found was somewhat surprising.  The problem turned out to be a simple (or not so simple) data type conflict.  I was placing a string time stamp into a channel that was had a time data type.  I had commented out the statement “On Error Resume Next” so that I would expose any errors but none were generated for that error.  Once I converted the string into a time base data type everything work and did not need your suggestion.  Again I want to thank you for your suggestion for without it I would not have been able to determine the cause of the problem. 

Elias

0 Kudos
Message 17 of 17
(1,378 Views)