the Known Issues - JCMS

JCMS Community Forum
Have your questions answered by JCMS professionals

note:  JCMS is fully functional when used with MS Access-32bit running on W7-32bit and W7-64bit Operating systems.  JCMS is currently not supported on MS Access-64bit.

The latest release of JCMS is v4.5.0 (released 06/18/2012)

note:  prior to running the JCMS installer, rename/move any existing databases named jcms_db.mdb
The JCMS installer will not install the new v4.5 database if another jcms_db is named in the database folder.

v4.4.0  released 12/28/2011

v4.3.0  released 10/25/2011

Pen Controls:
When you select a pen name, you do not always get the correct pen, especially if you type the name.  It also occurs when selecting pen names with the mouse. This bug occurs on the Edit Pen form, Add Mouse form, and Pen Info form in both MS Access and MySQL versions of the database. In part, it has to do with pen name sequences, such as name1, name2, name3, name12. When typing in the control, it cannot find name1, only name12.

v4.2.1  released  8/9/2011 

v4.1.2  released 10/8/2010

Handheld Wean, and Handheld Wean and Exit forms: 
When using MySQL, these forms may display the message "transaction rolled back: an error occured in ...  The message is misleading.  The error occurs because MySQL is unable to enter the wean date into the litter record.  The workaround is to use the Handheld Bulk Exit form to exit all the mice in the pen, and the regular Edit Litter form to enter the wean date.

Sample Locations:
1.       JCMS has a problem associating duplicate names. For example, if there are two “RoomA” locations, both containing a “Rack” location,  JCMS incorrectly assigns the second occurrence of “Rack” in a “RoomA” with the first occurrence of “RoomA”.
2.       If the “Rack” in RoomA is given a location description, JCMS will incorrectly display this same description for any “Rack” in a RoomA.
3.       If any location description is removed by updating it to be blank, JCMS will display an “Invalid use of Null” error and not change the location description.

v4.1.1

Multi-user concurrent connections: 
If a user runs a query and leaves the session open, additional users are then unable to open the JCMS interface file.  Fixed in v4.1.2.

v4.1.0

HandHeld-Add Litter w/Mice form:  when setting the wean date, be aware the datepicker calendar opens at year 2006 (fixed in v4.1.1).

HandHeld-Wean form:  a bug prevents the form from functioning (fixed in v4.1.1).

Edit Genotype form:  a 2nd allele is not required, but once one is added, there is no edit function to return it to blank/null.

v4.0.0 & 4.0.1

MySQL users only:  when using the following forms, the boolean values may be cleared (i.e. set to false).
          Edit Genotype - confidence checkboxes
          Edit Matings - needs genotyping checkboxes
          Edit Plug Dates - obsolete checkboxes
There is no workaround, however, these issues will be fixed in the next release (v4.1.0).

v4.0.0

Pregnancy Check report:  Matings without litters are not showing on the report (fixed in v4.0.1).

Bulk Add Mice form:  When the database is new, and no pens have been created, using the Bulk Add Mice form will generate an error (fixed in v4.0.1).

Cage Use Summary report:  When using the filter option to sort by strain, an error is generated if the strain name contains unusual characters (fixed in v4.0.1).

Plug Date report:  The DPC (date post conception) is missing from the report (fixed in v4.0.1).

v3.4.3

v3.4.0 & v3.4.1 & v3.4.2

MySQL users only:  when using the following forms, the boolean values may be cleared (i.e. set to false).
          Edit Genotype - confidence checkboxes
          Edit Matings - needs genotyping checkboxes
          Edit Plug Dates - obsolete checkboxes
There is no workaround, however, these issues will be fixed in the next release (v3.4.3).

v3.4.1

MS Access 2003 users: Wean Report does not work on upgraded databases (fixed with v3.4.2).

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 (fixed with v3.4.1).

v3.3.0 & v3.3.1

Wean Work Report:  The query for the wean report is looking up the pen ID for the sire. It should be looking up dam1's pen ID (fixed with v3.4.0).

Add Pen form:  adding text to a pen id will generate an error (fixed with v3.4.0).

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.

Colony Summary report:  the number of live mice calculated on the report is much lower than actual.  Fixed in v3.3.

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.