In the Windows edition, you can create an import information editing UOC routine in the following development environments:

• Microsoft Visual C++ Version 5.0 or later (preprocessor: 32-bit)
• Platform SDK February 2003 or later (preprocessor: IPF)
• Visual Studio 2005 or later (preprocessor: EM64T)

To create a DLL file:

1. Select a table that will use the import information editing UOC routine.
2. Select functions for your import information editing UOC routine; create these functions in the C language that is used to create application programs for Windows HiRDB. To issue SQL statements from the UOC routine, use the HiRDB preprocessor to expand the SQL statements into the applicable language. Datareplicator's UOC header file is stored in \include under the Datareplicator installation directory.
3. Compile and link the created functions to create a DLL file. To call the UOC routine from Datareplicator, you must create an interface function with the __cdecl calling convention, and then export it.
4. Specify in the import definition as an absolute pathname the name of the import information editing UOC routine.

This subsection explains how to compile and link a UOC routine in each development environment.

(a) Microsoft Visual C++ Version 5.0

If you use Microsoft Visual C++ Version 5.0 to compile and link your UOC routine, select Settings from the Project menu to specify options.

The following table lists and describes the items to be specified in Project Settings or Settings.

Table 8-1 Items to be specified in Project Settings or Settings in Microsoft Visual C++ Version 5.0

Item	Category	Category setting	Setting
Compiler	Code Generation	Struct Member Alignment	8 bytes
		Runtime Library	Multi-threaded DLL
		Calling Convention	_cdecl *
	Preprocessor	Include file path	Datareplicator-installation-directory\include
Linker	Input	Object/runtime module	CLTDLL.LIB (specify if SQL statements will be issued from the UOC routine)
		Additional library path	HiRDB-installation-directory\CLIENT\LIB (specify if SQL statements will be issued from the UOC routine)

If an unresolved link error occurs, specify all libraries required during linking.

(b) Platform SDK February 2003

• UOC routine compilation
  

  cl.exe /c /D_MT /D_DLL /MD /D"WINVER=0x0400" /D"_WIN32_WINNT=0x0333 /D"_WINNT" /D"NDEBUG" /D"_WINDOWS" /D"WIN32" /D"WIN64" /nologo /I Datareplicator-installation-directory\include UOC-source-file-name[UOC-source-file-name]...

• UOC routine linkage
  

  link.exe /subsystem:console /incremental:no /machine:IA64 /out: DLL-name-of-import-information-editing-UOC-routine /DLL /DEF:definition-file UOC-routine-object-name

  If SQL statements will be issued from within the UOC routine, the library specification HiRDB-installation-directory\CLIENT\LIB\CLTDLL.LIB is also required.
  

(c) Visual Studio 2005

If you use Visual Studio 2005 to compile and link your UOC routine, select Settings from the Project menu to specify options.

The following table lists and describes the items to be specified.

Table 8-2 Items to be specified in Project Settings or Settings in Visual Studio 2005

Item	Category	Category setting	Setting
Platform	--	--	Win32
Configuration Properties	General	Common Language Runtime Support	No Common Language Runtime Support
Compiler	Code Generation	Struct Member Alignment	8 bytes
		Runtime Library	Multi-threaded DLL
	Advanced	Calling Convention	_cdecl *
	General	Additional Include Directories	Datareplicator-installation-directory\include
Linker	General	Additional Library Directories	HiRDB-installation-directory\CLIENT\LIB (specify if SQL statements will be issued from the UOC routine)
	Input	Additional Dependencies	CLTDLL.LIB (specify if SQL statements will be issued from the UOC routine)

Legend:

--: Not applicable

If an unresolved link error occurs, specify all libraries required during linking.

• Check that the created UOC routine does not use the same memory mapped file that is used by the target Datareplicator or by any other system.
• If the UOC routine's processing results in an error, the name of the DLL file is displayed in the error log file as the program name.
• If you will be executing transaction control functions from the UOC routine to import data using the two-phase commit method, link the following import libraries provided by Datareplicator:
  Datareplicator-installation-directory\lib\hdsuif.lib
  
• If SQL statements are issued from the UOC routine, specify the HiRDB-provided include files and import libraries during compilation and linking. Also, select the appropriate import libraries according to the transaction control method.
  
  • One-phase commit method
    cltdll.lib
    
  • Two-phase commit method
    pdcltx32.lib