[AccessD] Word documents and MS Access

Hi Guys:

Nothing like a long weekend in which I planned to work in the garden and
then after 2 weeks of sun shine, nature decides it is a good time to water
things... real good.

That means more time to enjoy the computer.

Thank, Bryan, William, Stuart and Arthur. I will do a little more research
and maybe ask some more complex questions, if that is all right.

Jim 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Sunday, May 20, 2007 3:21 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Word documents and MS Access

100% correct, Stuart. I recently published an article about exactly this at
TechRepulic.comm. It doesn't apply specifically to Access; it was written
for the SQL Server crowd; but it may be convertible. No promises. I dealt
solely with the SQL 2000/2005 cases. In theory, the logic ought to work, but
I haven't tested it there.

Visit www.techrepublic.com and search for stuff by me; it ought to be the
first or second or third reference.

A.


On 5/20/07, Stuart McLachlan <stuart at lexacorp.com.pg> wrote:
>
> On 20 May 2007 at 13:20, Jim Lawrence wrote:
>
> > Hi All:
> >
> > I have two questions. They are both related. A client has approached me
> with
> > a particular project and I am wondering if anyone has experience with
> the
> > following:
> >
> > 1. Double-byte Character Sets; using them with Word documents and Access
> > databases.
>
> A real PITA.
>
> >From http://msdn2.microsoft.com/en-us/library/ms776454.aspx
>
> "Note: New Windows applications should use Unicode to avoid the
> inconsistencies of varied code pages and for ease of localization.
> However,
> some legacy protocols might require the use of DBCS code pages. Each DBCS
> code page supports different characters, but no page supportsthe full
> breadth of characters provided by Unicode. Each DBCS code page supports a
> different subset, differently encoded. Data converted from one DBCS code
> page to another is subject to corruption because the same data value on
> different code pages can encode a different character. Data converted from
> Unicode to DBCS is subject to data loss, because a given code page might
> not be able to represent every character used in that particular Unicode
> data."--
> Stuart
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com