Some LambTracker® Bugs

Note: this blog post was originally posted on lambtracker.com and has been moved here for preservation. Some information may be outdated.

We just finished our sheep experiment week. We are working with the USDA on developing non-surgical AI procedures for sheep. Last year, we successfully used LambTracker® to collect a ton of data on insemination depths, estrus characteristics, etc. However, since then, I’d added the days in age calculation to the EvaluateSheep function, and I did not test that the custom evaluations still worked. As a result, LambTracker® failed during the inseminations. I didn’t have time to debug it then, but I do now. I need to do some re-writing of the days in age code to get it working again. I reused a cursor that I thought was not being used at all, and that caused all sorts of database errors.

I’m also adding a lot of the desktop functions to create and set breeding records, both on the ram side and ewe side, which I did by hand last year. So far, that’s working fairly well, but it’s going slower than I’d like. Getting all the data in correctly is taking some time.

Scroll to Top