MatchUp Object:FAQ - Revision history

Admin at 00:45, 26 March 2022

2022-03-26T00:45:49Z

@@ Line 33: / Line 33: @@
 :;Linux Distributions:
 ::Red Hat 8.0 (gcc 3.3) and above 32/64 bit (x86, x64)
 ==Setting Up==

Admin at 17:12, 16 December 2016

2016-12-16T17:12:28Z

← Older revision		Revision as of 17:12, 16 December 2016
Line 84:		Line 84:
	:To initialize the MatchUp Object you must specify a valid License Key, path to the matchUp data files, the matchcode to be used in the process, and the location where each records matchcode key is stored. Without calling these methods (or setting as properties in some languages), the subsequent call to Initialize will return the respective error.		:To initialize the MatchUp Object you must specify a valid License Key, path to the matchUp data files, the matchcode to be used in the process, and the location where each records matchcode key is stored. Without calling these methods (or setting as properties in some languages), the subsequent call to Initialize will return the respective error.
	<blockquote>		<blockquote>
	<pre>matchup.SetLicenseString(~~license~~);		<pre>matchup.SetLicenseString(License Key);
	matchup.SetPathToMatchUpFiles(PATH);		matchup.SetPathToMatchUpFiles(PATH);
	matchup.SetMatchcodeName(MATCHCODENAME);		matchup.SetMatchcodeName(MATCHCODENAME);

Admin at 23:15, 15 December 2016

2016-12-15T23:15:48Z

← Older revision		Revision as of 23:15, 15 December 2016
Line 82:		Line 82:
	==Initialize and Configure==		==Initialize and Configure==
	===How do I initialize properly?===		===How do I initialize properly?===
	:To initialize the MatchUp Object you must specify a valid ~~license~~, path to the matchUp data files, the matchcode to be used in the process, and the location where each records matchcode key is stored. Without calling these methods (or setting as properties in some languages), the subsequent call to Initialize will return the respective error.		:To initialize the MatchUp Object you must specify a valid License Key, path to the matchUp data files, the matchcode to be used in the process, and the location where each records matchcode key is stored. Without calling these methods (or setting as properties in some languages), the subsequent call to Initialize will return the respective error.
	<blockquote>		<blockquote>
	<pre>matchup.SetLicenseString(license);		<pre>matchup.SetLicenseString(license);
Line 115:		Line 115:

	===What environment variables are available and why?===		===What environment variables are available and why?===
	:Currently, you can set MD_LICENSE. This environment variable is made available so that you can set your ~~license string~~ without recompiling your code.		:Currently, you can set MD_LICENSE. This environment variable is made available so that you can set your License Key without recompiling your code.


Line 126:		Line 126:
	#Click New.		#Click New.
	#Enter “MD_LICENSE” in the Variable Name box.		#Enter “MD_LICENSE” in the Variable Name box.
	#Enter the ~~license string~~ in the Variable Value box and then click OK.		#Enter the License Key in the Variable Value box and then click OK.

	:Please remember that these settings take effect only upon start of the program. It may be necessary to quit and restart the development environment to incorporate the changes.		:Please remember that these settings take effect only upon start of the program. It may be necessary to quit and restart the development environment to incorporate the changes.

	===How do I use MD_LICENSE Linux===		===How do I use MD_LICENSE Linux===
	:Unix-based OS users can simply set the ~~license string~~ via the following:		:Unix-based OS users can simply set the License Key via the following:
	<blockquote>		<blockquote>
	<pre>export MD_LICENSE=A1B2C3D4E5 (not the actual ~~license string~~).</pre>		<pre>export MD_LICENSE=A1B2C3D4E5 (not the actual License Key).</pre>
	</blockquote>		</blockquote>
	:After putting this setting in the .profile, remember to restart the shell.		:After putting this setting in the .profile, remember to restart the shell.
Line 140:		Line 140:


	===How many users can use my ~~license~~?===		===How many users can use my License Key?===
	:A single ~~license~~ generally allows a single computer to be running MatchUp. For questions regarding copyright, licensing, and multiple licensing (or site - licenses), contact Melissa Data Sales. This is an important topic beyond the scope of the FAQ.		:A single License Key generally allows a single computer to be running MatchUp. For questions regarding copyright, licensing, and multiple licensing (or site - licenses), contact Melissa Data Sales. This is an important topic beyond the scope of the FAQ.

	===Can I cut and paste the activation code from Windows into the AP or the opposite?===		===Can I cut and paste the activation code from Windows into the AP or the opposite?===
	;Answer:		;Answer:
	:The MatchUp Object ~~license~~ codes are NOT compatible with neither MatchUp for Windows nor the previous version, the MatchUp API. Do not try to cut and paste one of these other ~~license~~ codes into the MatchUp object, you will get an invalid ~~license~~ error.		:The MatchUp Object License Key codes are NOT compatible with neither MatchUp for Windows nor the previous version, the MatchUp API. Do not try to cut and paste one of these other License Key codes into the MatchUp object, you will get an invalid License Key error.

Admin at 22:09, 21 June 2016

2016-06-21T22:09:45Z

← Older revision		Revision as of 22:09, 21 June 2016
Line 35:		Line 35:

	==Setting Up==		==Setting Up==
	===What is the difference between the COM and Standard version of MatchUp Object?===		===What is the difference between the COM and Standard version of MatchUp Object? (Deprecated 2628)===
	:There are essentially no differences in the underlying code for the COM version and the Standard version of MatchUp Object. The COM version has a COM interface layer used to communicate between your code and MatchUp Object, and it is supported by many different languages. The Standard version of MatchUp Object is an unmanaged dll that must be included into your program which eliminates the extra latency created by the COM layer.		:There are essentially no differences in the underlying code for the COM version and the Standard version of MatchUp Object. The COM version has a COM interface layer used to communicate between your code and MatchUp Object, and it is supported by many different languages. The Standard version of MatchUp Object is an unmanaged dll that must be included into your program which eliminates the extra latency created by the COM layer.


	===How do I install the COM version DLLs?===		===How do I install the COM version DLLs? (Deprecated 2628)===
	:On a 64 bit machine you will have to manually register the 64 bit COM dll.		:On a 64 bit machine you will have to manually register the 64 bit COM dll.

Admin at 21:38, 21 June 2016

2016-06-21T21:38:30Z

← Older revision		Revision as of 21:38, 21 June 2016
Line 40:		Line 40:

	===How do I install the COM version DLLs?===		===How do I install the COM version DLLs?===
	:~~Running the DVD or demo installation will automatically register the 32 bit COM Objects.~~ On a 64 bit machine you will have to manually register the 64 bit COM dll~~, as by default, only the 32 bit version gets registered~~.		:On a 64 bit machine you will have to manually register the 64 bit COM dll.

Admin at 21:26, 21 June 2016

2016-06-21T21:26:24Z

← Older revision		Revision as of 21:26, 21 June 2016
Line 14:		Line 14:

	===What do I need to do when installing the MatchUp Object DVD?===		===What do I need to do when installing the MatchUp Object DVD?===
	:When you install the MatchUp Object DVD, please pay attention to changes.txt on the root of the DVD. It will contain any changes that have been made to the object which may require you to rewrite/recompile your application. Also, when using the wrappers in the Interfaces folder, please read the readmes for each wrapper you are using as they may contain changes to the build process you have to make~~. Running the setup.exe will automatically register the 32 bit COM version, even on a 64 bit machine~~. You will have to manually register the 64 bit COM version		:When you install the MatchUp Object DVD, please pay attention to changes.txt on the root of the DVD. It will contain any changes that have been made to the object which may require you to rewrite/recompile your application. Also, when using the wrappers in the Interfaces folder, please read the readmes for each wrapper you are using as they may contain changes to the build process you have to make. You will have to manually register the 64 bit COM version.

Admin at 22:41, 11 March 2016

2016-03-11T22:41:25Z

← Older revision		Revision as of 22:41, 11 March 2016
Line 1:		Line 1:
			[[MatchUp Object\|← MatchUp Object]]
	{{CustomTOC}}		{{CustomTOC}}


	~~[[MatchUp Object\|Back to MatchUp Object Main Page]]~~

	==General==		==General==

Admin at 21:04, 15 July 2015

2015-07-15T21:04:11Z

← Older revision		Revision as of 21:04, 15 July 2015
Line 35:		Line 35:
	:;Linux Distributions:		:;Linux Distributions:
	::Red Hat 8.0 (gcc 3.3) and above 32/64 bit (x86, x64)		::Red Hat 8.0 (gcc 3.3) and above 32/64 bit (x86, x64)

	~~:;Solaris™ versions:~~
	~~::Solaris 8,9,10, SPARC platform, 32/64 bit.~~

	~~:;AIX™ versions:~~
	~~::5.2, 5.3. POWER, rs/6000, PPC, 32/64 Bit~~

	~~:;HPUX™ versions:~~
	~~::11.11, 11.23, PA-RISC, Itanium, 32/64 bit~~

	==Setting Up==		==Setting Up==
Line 141:		Line 132:
	:Please remember that these settings take effect only upon start of the program. It may be necessary to quit and restart the development environment to incorporate the changes.		:Please remember that these settings take effect only upon start of the program. It may be necessary to quit and restart the development environment to incorporate the changes.

	===How do I use MD_LICENSE Linux~~/Solaris/HP-UX/AIX~~===		===How do I use MD_LICENSE Linux===
	:Unix-based OS users can simply set the license string via the following:		:Unix-based OS users can simply set the license string via the following:
	<blockquote>		<blockquote>

Admin: Admin moved page FAQ:MatchUp Object to MatchUp Object:FAQ without leaving a redirect

2014-06-12T21:32:40Z

Admin moved page FAQ:MatchUp Object to MatchUp Object:FAQ without leaving a redirect

← Older revision	Revision as of 21:32, 12 June 2014
(No difference)

Tim: /* General */

2014-02-27T18:33:49Z

General

← Older revision		Revision as of 18:33, 27 February 2014
Line 1:		Line 1:
	{{CustomTOC}}		{{CustomTOC}}


			[[MatchUp Object\|Back to MatchUp Object Main Page]]

	==General==		==General==
Line 41:		Line 44:
	:;HPUX™ versions:		:;HPUX™ versions:
	::11.11, 11.23, PA-RISC, Itanium, 32/64 bit		::11.11, 11.23, PA-RISC, Itanium, 32/64 bit


	==Setting Up==		==Setting Up==