N
Neil Burnett
I have a Jet (an Access 2000 .mdb) backend to a website that uses
charset=utf-8 in the meta tag of the data input form web page and the
viewing web pages. This works fines - even on an NT server with SP6a,
contrary to most of what I have read about IIS 4,0 and Unicode. (I
don't seem to need @CODEPAGE directives in the ASPs so I don't use
them.)
Data is cut and pasted from a wide variety of differently encoded web
pages - Big5, EUC, Shift JIS, Windows-1250/1/2/3, iso-2022-xx etc. -
and IE6 seems to convert it accurately and send the data to the
database in one unified encoding. I don't what this encoding is - I
think it could be utf-16 - but it all gets sorted out nicely for me.
This means I can get data that originated in different encodings - yet
stored in the same database field - to display on the same web page
correctly. IE6 and Netscape 7.1 even sense which fonts to use. Great!
When I use MS-Access 2000 forms to view and edit this data instead of
a web form, the story is not the same. I am unable to work out how to
view and edit the data in the appropriate encoding.
For now, as a workaround, I am writing database editing web pages to
manage every table in the database, but I would really like the users
to be able to edit data directly using an Access form as well as a web
interface. I have searched Access 2000 for an encoding setting but
cannot find one. All suggestions gratefully received.
charset=utf-8 in the meta tag of the data input form web page and the
viewing web pages. This works fines - even on an NT server with SP6a,
contrary to most of what I have read about IIS 4,0 and Unicode. (I
don't seem to need @CODEPAGE directives in the ASPs so I don't use
them.)
Data is cut and pasted from a wide variety of differently encoded web
pages - Big5, EUC, Shift JIS, Windows-1250/1/2/3, iso-2022-xx etc. -
and IE6 seems to convert it accurately and send the data to the
database in one unified encoding. I don't what this encoding is - I
think it could be utf-16 - but it all gets sorted out nicely for me.
This means I can get data that originated in different encodings - yet
stored in the same database field - to display on the same web page
correctly. IE6 and Netscape 7.1 even sense which fonts to use. Great!
When I use MS-Access 2000 forms to view and edit this data instead of
a web form, the story is not the same. I am unable to work out how to
view and edit the data in the appropriate encoding.
For now, as a workaround, I am writing database editing web pages to
manage every table in the database, but I would really like the users
to be able to edit data directly using an Access form as well as a web
interface. I have searched Access 2000 for an encoding setting but
cannot find one. All suggestions gratefully received.