known issues - the JCMS Colony Management System

JCMS Community Forum
Have your questions answered by JCMS professionals

v3.4.1

v3.4.0

Edit Mouse form:  changing a mouse ID while unsubmitted changes remain on the form, resulted in the new mouse ID being updated with the unsubmitted changes.

v3.3.1

Add Pen form:  adding text to a pen id will generate an error.

v3.3.0

The following issue affects JCMS Sample Tracking forms, v3.0.0 through v3.3.0:
   A recent Microsoft security patch caused a problem with one of the features we use in the Sample Tracking module of JCMS.
   Microsoft recently released a fix which we have bundled into an installer which you can download and run on your computer.
   If you get a run-time ‘2926’ error message when you try to work with any of the Sample Tracking forms, download and install this patch:

Edit Mouse form:
A mouse ID can get out of synch with data displayed on the form.  This can cause confusion to an observer, and if a user presses submit, the mouse update can apply incorrect information for the mouse.  Fixed in v3.3.1

All forms:
Some forms display larger than necessary:  You can just resize the form and save the form from the File menu to resize the form permanently.

v3.2.1

Handheld Change Life Status form: date handling code has bug.

Edit Mouse form: should display genotype controls even when there are none.

v3.2.0

Sample Locations: In JCMS release 3.2.0 a bug was introduced that incorrectly assigned sample location for the sample.   This issue would only arise under specific conditions.

First, you must have multiple location names associated with the same base location. For example

TJL
  --Building1
       ----Room1
       ----Room2
  --Building2
       ----Room1
       ----Room2

It is intuitive to have unique name for buildings for your campus, however inside the building you may have similar room names in all your buildings.  The bug would assign all Room1 locations to the first Room1 defined, in this case Building1\Room1

This issue is resolved with the 3.2.1 release however if you have added or edited you samples with the 3.2.0 version of the software and have a similar structure as the example above, please contact us (cjd@jax.org) for help resolving this issue.

Mouse Line Viability report:  If using msOffice2003, when exiting the application, or when running a MLV report while non-MLV reports are open or minimized, select ‘no to all’ at the message prompt.  MLV report will then run normally.

Add Litter w/Pups form:  After any user generated error message, Wean/Tag dates become checked, and the date field changes to default date.

Wean form:  If you are using the Wean form and the Add Litter w/Pups form, the maxAutoMouseID can get out of synch.

v3.1.0

Add Litter w/Pups form:  After any user generated error message, Wean/Tag dates become checked, and the date field changes to default date.

Add Sample form:  Error in adding Activated Matings as source. 

Edit Sample form:  Error in editing Activated Matings as source.

Wean form:  If you use the Wean form and the Add Litter w/Pups form, the maxAutoMouseID can get out of synch.

Cage Cards:  Protocol ID does not print on cage cards.
     
Add Exp Test form:
Repeat-Test Button - When you select the button, it puts the age in days, but does not set the radio button to days. So if you working in weeks, you might end up with 52 weeks when you meant 52 days.

Add Exp Data form: If the Proposed Date is null in the database, an "invalid property value" error occurs.
                               
Query Samples form:

  • If a sample's Preservation Type, Method, and/or Detail are null (blank), then that sample's data is left out of query results.
  • There are instances when JCMS locks up when you attempt to run a sample query.
  • When querying by Sample Storage Location, the Sample Query form fails to produce the correct results, and/or pops up a debug-end message.