AquilaCRS FAQ

This topic is for iBID

This is a Technical (IT) Helpdesk topic

This page covers known issues in the AquilaCRS/iBID desktop software.

AquilaCRS Desktop version 1.2.4

No known issues.

AquilaCRS Desktop version 1.2.2

No known issues.

AquilaCRS Desktop version 1.2.0

Ensuring desktop v1.2 is installed before server v1.2

IBID desktop v1.1 is not 100% compatible with ibid server v1.2. The format of the in-patients list changed and so users on v1.1 desktop will not be able to see the in-patients list and the error #Format of the data in the stream doesn't match the destination table format occurs

No ability to create or edit records

Severity: New Feature

Symptom: When the IBID desktop software is automatically upgraded users cannot create or edit records. Query options are also unavailable.

Solution: An iBID admin user must grant permissions to users. In emergency cases the user can be given an admin user code to it themselves. See Managing_Users#User_Permissions.

Format of the data in the stream doesn't match the destination table format

Severity: High

Full error message: Format of the data in the stream doesn't match the destination table format. The TRAUMA_NETWORK_ID field isn't found. The RECORD_DATE_TIME field isn't found. (EDAException)

Cause: The user has not been upgraded and is still running a client v1.1 but their AquilaServer has been upgraded to v1.2.

Solution: The users' IBID software needs upgrading to v1.2.1. See How to make sure your software is up to date for details on how to achieve this.

Dates are not sorting correctly in Query Results

This is a known issue in v1.2.1. The problem has been identified and a fix will be issued as v1.2.2 in late August 2014.

The workaround is to export to Excel as the date fields export correctly.

Error store actLargeIBIDView

Severity: Very Low

Cause: Known issue in v1.2.0

Solution: Upgrade to v1.2.1

Error store actToggleFitWidth

Severity: Very Low

Cause: Known issue in v1.2.0

Solution: Upgrade to v1.2.1

Access Violation when tabbing through date fields

Severity: Low

Cause: Known issue in v1.2.0

Solution: Upgrade to v1.2.1

Access Violation when moving IBID records

Severity: Low

This is a known issue, currently only encountered in QA. The error occurs at the end of the move process, after all records have been moved.

A fix will be issued as part of v1.2.2.

See Also

• How to make sure your software is up to date
• Aquila Software Status
• AquilaCRS Whats New
• IBID Version 1.1 FAQ
• Managing Users