|
Known ITEMS as of
2008.5.21 |
|
1 |
For some
reason, on SOME PCs running
Win'XP-SP2 or Win'2003-SP2, the Data Execution
Prevention feature prevents various programs,
including ContactGenie, from starting or an immediate
Access Violation error is encountered.
While this is an
infrequent issue, if it occurs on your system, please follow the steps described
here or in the <CGStartUpError.htm>
document located in the program install directory (as of 2007/12/12) |
|
2 |
Processing of Outlook folders as
input data sources can be an
extremely slow process especially when processing a very large
contact datasets. Performance enhancements are expected with the
next major release of ContactGenie DataPorter. |
|
3 |
Header row in text files cannot contain multi-line field
names |
|
Build 2.0.210 - released 2008.5.21 |
|
1 |
Correct error importing fields containing NULL values
while in <add> mode (introduced in version .209) |
|
Build 2.0.209 - released 2008.5.9 |
|
1 |
Added option to determine whether Blank/Empty or Null
input fields either replace corresponding Outlook fields or treated as
no update info available for the field. Option applies to all fields in
the field map and cannot be individually set. |
|
2 |
Template database updated to version 2.0.3 to accommodate
above changes. Existing template databases will be automatically and
dynamically update the first time program run. |
|
3 |
Internal component updates |
|
Build 2.0.208 - released 2008.4.8 |
|
1 |
Fixed problem related to using custom fields as update
keys in conjunction with partial field updates (i.e. street/phone number
fields) |
|
Build 2.0.207 - released 2008.2.12 |
|
1 |
User-defined fields for contact folders not using a
default custom form now extracted from the "User-defined fields in
folder list" |
|
2 |
MS SQL list of tables now includes tables for all
owners/schemas and not just those for "dbo" |
|
3 |
Corrected issue related to some field types not correctly
handled for MS SQL/MySQL tables |
|
Build 2.0.206 - released 2007.11.6 |
|
1 |
Corrected issue selecting default message class in
folders containing contacts with multiple message classes and first
contact in folder had message class different then the default for the
folder |
|
Build 2.0.205 - released 2007.9.14 |
|
1 |
Corrected error when importing from MDB files without
using template. |
|
Build 2.0.204 - released 2007.8.10 |
|
1 |
Corrected error when importing "OtherAddressStreet" field |
|
2 |
Standard Outlook fields "User1-4" included in list of
text fields to be imported when size > 255 characters |
|
Build 2.0.203 - released 2007.8.1 |
|
1 |
Corrected issue for MS SQL '2005 servers not being found |
|
2 |
Fixed issue where empty contact item added to folder when
importing to an <empty> contact folder or one not containing a contact
assigned to the default message class for the folder |
|
Build 2.0.202 - released 2007.3.8 |
|
1 |
Native support added for MS Access '2007 (.accdb) and MS
Excel '2007 (.xlsx, .xlsm) input file types. Only first 255 columns will
be processed in Excel '2007 worksheet/range. |
|
2 |
Corrected issue when emptying contact folder prior to
importing |
|
3 |
Corrected problem displaying custom field info after
selecting folder on custom form info. |
|
Build 2.0.201 - released 2007.2.2 |
|
1 |
Various internal component updates |
|
2 |
Updated internal OS version recognition for error
reporting to include Microsoft Vista |
|
Build 2.0.200 - released 2006.11.26 |
|
1 |
CDO usage
eliminated and no longer a requirement. |
|
Build 2.0.196 - released 2006.10.03 |
|
1 |
Fixed problem
with one double quote mark within a field in a custom-delim text file |
|
Build 2.0.195 - released 2006.5.31 |
|
1 |
Visual FoxPro
OleDB driver (vfpoledb.dll) must be installed in order to process any
.DBF file. If not installed - option will not be visible for selection. |
|
2 |
Added option to <auto-map> multi-part street addresses
and phone numbers (information contained in updated help file) |
|
3 |
Added MS SQL '2005 Native Client support |
|
Build 2.0.194 - released 2006.3.12 |
|
1 |
Change to
handle category fields greater then 255 characters similar to Body
(Notes) field. All other text fields must be <= 255 characters. |
|
2 |
Corrected problem with "Clear Folder at start" not
displaying status correctly when recalling template. |
|
3 |
Added additional error messages if input data file not
found when recalling a template for improved explanation. |
|
Build 2.0.193 - released 2005.10.31 |
|
1 |
Corrected
problem encountered with empty un-intialized rows inside of an Excel
data range |
|
2 |
Enhanced error msg for SQL servers not being found to
reflect actual revision level of SQL driver |
|
3 |
Corrected problem related to custom forms with extraneous
fields. |
|
Build 2.0.192 - released 2005.08.05 |
|
1 |
Corrected
issue with using MS SQL as input data source without first saving
template (issue specific to MS SQL in CGD Pro Edition) |
|
2 |
Added Email?DisplayAs fields as importable fields for MS
Outlook 'XP - and '2003 (see updated help files for Outlook limitations
& requirements). This field will not appear for users of Outlook '2000. |
|
Build 2.0.191 - released 2005.07.10 |
|
1 |
Outlook folders used as input data sources no longer are
read completely when opening a previously opened template or when
changing select criteria |
|
2 |
Corrected some issues related to creation of CSV files |
|
3 |
Added capability to stop import processing via the UI
once started |
|
Build 2.0.190 - released 2005.06.23 |
|
1 |
Corrected problem with importing (and saving to CSV)
Outlook fields contained in Outlook folders used as the input data
source and containing invalid "recordset" field name characters.
|
|
Build 2.0.189 - released 2005.06.07 |
|
1 |
Corrected problem when using NUI folder type without
saving template, |
|
Build 2.0.188 - released 2005.05.01 |
|
1 |
Corrected error caused when MS Access input file
contained spaces in the MDB file name |
|
2 |
Corrected error when using the Reject Key option |
|
Build 2.0.187 - released 2005.04.18 |
|
1 |
Corrected issue when importing multi-part <mailing street
address lines> |
|
Build 2.0.186 - released 2005.04.10 |
|
1 |
Changed import of mutli-part phone numbers so that
"extensions" (where applicable and used) are prefixed by an "x" instead
of "-" enabling automatic Outlook formatting |
|
2 |
Corrected minor mapping issues related to multi-part
phone numbers for several "generally unused" phone numbers |
|
3 |
Corrected issue specific to Outlook '2003 when input data
sources included "birthday" and "anniversary" fields when in "add" mode
causing Outlook to report an update failure |
|
Build 2.0.184 - released 2005.02.24 |
|
1 |
Resolved issue of random contacts being added even if "Do
Not Update Outlook" option selected |
|
2 |
Corrected delimitor issue for CDH and CDN files |
|
3 |
Corrected issue with user-defined fields not being picked
up correctly when no custom form is used |
|
4 |
Corrected
issue when an Outlook numeric data-type user-defined field was used as
an update key |
|
Build 2.0.182 - released 2005.01.20 |
|
1 |
Corrected issue with multi-part
addresses not eliminating interspersed blank lines contained within the
input fields
(i.e. line 3 = blank within a 4 line address) |
|
Build - 2.0.180 - released 2005.01.11 |
|
1 |
When using [RUNTIME] constant in
select criteria (which gets replaced with date a template is run), added
capability for [RUNDATE] +/- # of days |
|
2 |
[RUNDATE] can only be used with
fields that are of the date or datetime
data type |
|
3 |
fixed issue with selection
criteria when using Outlook folder or Visual FoxPro as the input data source |
|
4 |
fixed issue with selection
criteria when using Outlook folder or Visual FoxPro as the input data source |
|
5 |
fixed issue where CSV field data
for boolean fields was showing the words "TRUE/FALSE" if run without the
template being saved first. Boolean field data will now always show as 0 or
-1 in the created CSV file |
|
6 |
fixed issue when clearing field
map list if no records contained in the target contact folder |
|
7 |
misc internal component updates
|
|
Build 2.0.178 - released 2004.12.15 |
|
1 |
corrected issue with date fields
defaulting to <current date> when used as part of selection criteria |
|
Build 2.0.177 - released 2004.11.23 |
|
1 |
corrected issue related to <PreScan>
if template was not saved first |
|
2 |
corrected issue related to an
input contact folder data source with
multiple message classes if the
template was not saved first |
|
Build 2.0.175 - released 2004.10.22 |
|
1 |
fixed issue related to fields
with embedded single quotes and used
as an update key field |
|
2 |
corrected issue related to
user-defined field names from an Outlook
contact folder when used as an input data source |
|
3 |
fixed issue preventing selection
criteria from being modified after
template saved initially |
|
4 |
fixed problem when Outlook folder
contained more then 255 fields and
user-defined fields containing illegal recordset field name characters
were not being cleared internally. When more then 255 fields are encountered
in an Outlook datasource, can no longer clear all fields and update the
template list unless at least one field has been selected. |