Quote from rb on 11/22/08 at 19:18:16:
 
if properly connecting to ecco, for most folder types they should.  
 
(not likely the cause but potentially related, there is a small known bug in slang dde that doesn't handle multiple item single folder mods,  if they are doing this,  the values are not being updated so likely you'd notice).
 
eg., MagicView should also be triggering.
 
Quote:

 
you should *only* see that if you have non-English characters.
 
cannot yet access the Font info of items externally,  so have no idea what CODE PAGE,  non-English data is supposed to be.
 
if you are all English and *still* get the dialog,   tell me more!  (maybe even post an example .eco  [with .doc included as item] that gets you there).
 
Quote:

 
currently we cannot touch the folder structure.  (we can see but not touch).
 
best alternate solution is a 'form' template with 'blank' folders pre-positioned.
 
this is possible to do,  but not seem like great solution usually.
 
 

Quote from rb on 11/23/08 at 16:32:23:
 
hmm.. that would seem odd... you're trying to merge a blank doc,  should not get any message at all.
 
 
Quote:
 
 
MM has an (undocumented) option to look for "MM_Blank" folders, and use those for logging merges.  you can copy and paste (even hundreds) of MM_Blank  folders under the MailMerge Tracking folder to create a ready-to-use form.
 
 
Quote:

 
interesting.
 
1.30 should not really be merging single items,  does it ?
 
 

interesting.
 
activated the MM_Blank option (ie., download latest), and updated manual.
 
 
will look at the single item blank form issue.
 

Quote from rb on 11/23/08 at 22:14:48:

 
 
after 1.30 using very different base to communicate inside Ecco.  That could be part of issue,  *but*,
 
I can't duplicate what you're seeing.
 
 
am only getting  the dialog when supposed to,  eg. non Enlgish characters and need the code-base.
 
 
you might try a systems reboot  (or try on another system).    
if that not change result,  try on clean file in non-slang extension.
 
also try to save under new name the merge template.
 
 
if you try with different data sets (phonebook as filtered, items selected, etc.)  still *always* get conversion dialog box ?
 
 
try also adding/ (or if was already there, removing )  itemtext to the merge fields,  see if impacts at all.
 
 
try also from clean (shift + new) file and see if any different.
 
 
 
 
(but  in all tests,  include at least one ACTUAL field... such as E-Mail or something..)
 
ps: the field you select could impact result.  Eg., if there is hidden garbage in some field,  that is non-english and will trigger the conversion dialog.  The new ecco interface may be either (1) adding its own garbage to the nice file data,  or (2) correctly reading garbage which was not read previously.  (or other issues may be at play).

Quote from rb on 11/24/08 at 21:08:05:
 
 
fantastic bug diagnosis.   (will look into deeper).
 
Quote:
 
 
 
Yes,
 
non-visible changes are usually made to the template file.  One of the purposes/uses of this is to allow access within merge to info otherwise not possible.
 
for example
 
{ DocProperty EMRecordCount }  is an example field you can use that accesses a 'hard' 'hidden' template property, the EMRecordCount.   Can do much in merge automation knowing how many records (for example including a FOOTER!).   This is addressed in MM help.
 
On each merge the template file updates (in memory, not on disk) with the new properties,  in this example,  the active record count and other info relevant to merge.
 
 
Part of what is so cool about this is the things you can do with MM that otherwise not possible.  Control of date field output styles,  on-the-fly merges,  report merge footers, auto changing merge text based on % of merge run complete.  (eg. sending 30% of list X text, 30% Y text, and 30% z text).   You can also build in messages etc. generated to operator by Word,  based on reaching end of merge run, etc.
 
when running merge on template from disk,  should not have any issue about closing.
 
 
Edited:

Quote from rb on 11/25/08 at 14:56:43:

 
 
and you sure if you use older version on same tests that you do NOT get the conversion window ??  

 
ok,
 
in looking at slang trigger issue,  realized we could access more & better folder & item data...
 
but like those dwarfs in Lord of the Ring,  dug too deep, and started sending data that confused the conversion routine.
 
So,
 
since the windows conversion routine seems beyond exact control,
 
wrote a new one from scratch.
 
 
 
now... (i hope!) we resolve the issue.... FOREVER!!
 
(but await your test results).
 
 
Codepage selection is now fully internal option.  For those who use it,  it's darn cool.
 
 
checkout v3.6B download.
 
(also added to eccotools.com magicMerge thread links to html and pdf instruction manuals.)
 

Quote from rb on 11/26/08 at 13:52:35:

 
indeed, that is a bug in error condition handling,  fixed in next release (not posted).
 
try a merge with SOME DATA!!
 
(ie. you don't need to do merge is you've not got any data to merge.....)
 
 
if you have *any* data in the merge does it work smoothly ??
 
 
 

Quote from rb on 11/26/08 at 15:24:10:

 
actually,  not need additional text in word,  just a value in folder in ecco to merge with.
 
 
you are getting a unicode conversion window.   That is interesting.
 
try closing down windows and creating & saving a file with new file name (that has never been used before).
 
if you merge that with records that contain some data (eg. use company but merge the entire 'default' phonebook).
 
still getting the conversion message ?
 
on first run also (?)
 
 
Edited:

 

Quote from rb on 11/26/08 at 19:48:05:

 
 
ok,  we try again!
 
 
download latest,
 
try w/ default, and with -1 codepage.
 
 
in theory this version should not change anything from old,
 
but then again v 3.0 and 3.2 shouldn't produce different results (in theory!).
 
 
so... if this works,  (or not)  Let me know...
 
(if it works need one more version to test to confirm have isolated issue).