MySqlTalk.com  

Go Back   MySqlTalk.com > Navicat - MySQL management tool > Navicat Support
User Name
Password
FAQ Members List Calendar Search Today's Posts Mark Forums Read


Reply
 
Thread Tools Search this Thread
Old 11-06-2006, 11:52 AM   #1
Walleye
Junior Member
 
Join Date: Nov 2006
Posts: 2 Walleye is on a distinguished road
Importing Access DB mail merge select recipients wrong if using Unicode Compression

Howdy,

When I imported from Access and then used MySQL with Word Mail Merge and try to select recipients it had some of the fields data scrambled or moved to other fields... I can cure this by turning off (in Access) "Allow Unicode Compression" in the field before I import to MySQL via Navicat...

The problem is there are about 100 fields to turn this off in... is there a good way to do this either in Access before I import or let Navicat know that Unicode Compression was used on the imported database ???

Thanks for any help, it wont take too long to do it by hand but learning is a good thing...

Wally


PS Complaint... you would think that after 10 years of MS knowing this is an issue (Word recipient selection with Unicode Compression) you would think they would have addressed it...
Walleye is offline   Fork this post Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump



All times are GMT -4. The time now is 06:39 AM.



Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited.
Google
  Web http://www.mysqltalk.com
DISCLAIMERS:
1. We have no commercial interest in this site.
Banner Ads and Subscriptions will only be used to help pay for hosting and maintenance costs.
2. MySQLTalk.com is NOT affiliated with MySQL AB in any way.
3. MySQLTalk.com is NOT endorsed by MySQL AB in any way.
4. Please do not post any content that is harmful to MySQL or MySQL AB, meaning no misleading or obsolete information will be tolerated.
Well-founded constructive criticism meant to help the community is permitted.
5. This website is founded with the goal of improving the MySQL community.
We not only tolerate newbies, we encourage them.
Please do not ask newbies to "read the manual".