Showing posts with label Problems. Show all posts
Showing posts with label Problems. Show all posts

Wednesday, September 1, 2010

HL7 Mapper may not save configuration due to missing access to INFORMATION_SCHEMA

Symptom: When trying to save configuration, an error message is shown with the following text:
"Object Reference not set to an instance of an object"
Reason: The HL7 Mapping application relies on SQL Server INFORMATION_SCHEMA to generate the database view dynamically. Apparently there has been some compatibility issues with this feature since SQL Server 2005 and sometimes there's no access to this view.
The view may be accessible on one catalog and not accessible on another even if they are on the same table.
If this

Solution: We are working on a fix to this problem.

Ticket 224: HL7 Mapper may not save configuration due to missing system tables



Thursday, June 17, 2010

FIX Problem: RZDCX not showing in the Add reference tab in Visual Studio 2008

Unfortunately, a problem was found in the registration of the win32 build 1.0.1.4.
The problem seams to be related to win32/x64 registry entry mix-up in the type library registry entry leading to the component not showing when trying to add a reference in C# projects.
This problem is showing in build 1.0.1.4 and 1.0.1.3.

The problem is now fixed in build 1.0.1.5

Note that for using the win32 component on x64 machines you should use the SysWOW32o64 version of regsvr32.exe

Sunday, April 19, 2009

Win32 registration problem in v 1.0.0.5

A problem registering and using version 1.0.0.5 from the download page was reported.
Please use the updated v 1.0.0.6 patch from the download page.

Monday, March 30, 2009

Known bug: Linking tables using same key field

The following problem was reported and identified ion HL7Kit Pro.
The program fails to identify a parent-child relationship between two tables where the relationship columns have the same name for example if two tables have a foreign key where the primary key column name is 'id' and the foreign key column is also called 'id'.

Workaround: rename one of the columns.

Ticket #: 146