Later Error that occurs!!

[dsg1]

Yes Randy, I got it working with Mike's example.  I did not try the combo box approach as I'd already got it working just before your first post.

I do appreciate the help though... both from yourself and from mike as well.  No need to add on to this thread unless people just want to show other ways that they import excel spreadsheet information in case another person wants to see how its done, perhaps I can post my final code statement here when I get a few more control panel quotations done.

Thanks again,

Jerry

[dsg1]

I've run into this with both 5.0 and 5.1.  When using the data table object and the multiple variable to select a "year", "Month" and "Day" to bring up daily information, every once in awhile the Lookout program just stops updating.  It locks in on a day and regardless of if you change the year, month or day, eithe rof my reports just remain locked on the day or month that was last viewed.  They hypertrend and other display information continues to work, just not that data table.

I know a workaround, but not a fix as of yet.  I know that if I close lookout and recopy lookout.exe from a 2nd location over the one is to be used, it works again.

Does anyone know of a fix, I know its an older version and thus NI didn't sound like they wanted to help unless I updated to a newer version to see if that would resolve the problem.

My thoughts were that it might be some sort of cache or file size adjustment in the .ini file.

Message Edited by dsg1 on 04-04-2007 12:42 PM

[Ryan.S]

I tried to reproduce this error with Mike's example, but failed. I kept updating the SQL parameters to load different files, the datatable worked fine.

How large is your csv file?

If you only run the Mike's example, will the error occur after a while?

[dsg1]

I do not know the exact size, but it is not very large.  Every hour I save 4 registers and then again at the end of the day I save them to a 2nd file.  Thus I have a daily report with hourly values and a monthly report with daily values.  The time duration that this occurs varies, sometimes it goes 2 weeks, sometimes it takes a few months before the problem repeats.  Thus I'd have to say i'm not very surprised at all that you did not have a repeat of the problem within a window of just a few days.  I'll be visiting the customer today to patch the problem.  Due to the various long term time frame between problems it is really hard to tweak, I could go two months before the problem would show back up, and normally tech support would have closed the case and ask me to restart a new case #.  My customer has more or less been dealing with this for 2 years now and felt that the update from his previous system was a setback because he did not have the problem with the 4.01.b version. 

Would the fact that I made a second process that looked at the variables from the first process make a difference?  I've considered going back and putting all of the code in one process, but have not tried that as of yet.