RTF control

[SF]

Hi,

I have a database for recroding proposals in my unit. Each proposals has a
descriptive part that use Khmer script (thru legacy font).

Since Access does not handle RTF very well (limited to legacy font), I have
opted to use FMS's Total Access Memo.

I want to know whether Total Access Memo is fit for using with Access 2003?
or if someone has any problem using Total Access memo is the past?


SF

 

[Tom Wickerath]

Hi SF,

I have Total Access Memo for Access 2002. It works fine for most of my
needs, although it does not support Unicode. So, for example, you cannot have
rich text with Chinese, Japanese, Korean or any other language that requires
Unicode. (My wife was rather disappointed with this limitation, as she is a
Korean-American).

There is also a free RTF control available on Stephen Lebans' web site. It's
not as full-featured as Total Access Memo, but it's also not as expensive
<smile>

http://www.lebans.com/richtext.htm

Access 2007 includes built-in support for rich text, as long as you are
using the newer ACE (.accdb) file format. However, a major 'gotcha' is that
they choose to store the text as HTML. Therefore, there is no smooth
migration path from an earlier version Access app. that includes either TAM
or Stephen's control to use the built-in support. You would have to manually
re-enter all of the rich text to use the built-in capability in Access 2007.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Neil]

I use it with A03, and haven't had any problems.

 

[Neil]

Hi SF,

Access 2007 includes built-in support for rich text, as long as you are
using the newer ACE (.accdb) file format. However, a major 'gotcha' is
that
they choose to store the text as HTML.

And the fact that there's no programming interface for the HTML. All codes
need to be applied using custom code -- not a problem for adding simple
code; but a bit of a pain for complex codes or for removing codes.

Therefore, there is no smooth
migration path from an earlier version Access app. that includes either
TAM
or Stephen's control to use the built-in support. You would have to
manually
re-enter all of the rich text to use the built-in capability in Access
2007.

Yeah, seems that it would be simpler just to upgrade to TAM for 2007 when
it's out.

But if one were to convert to HTML, seems to me that a fairly simple
approach would be to export to Word; save as HTML; and then bring the HTML
codes into Access. Seems to me that some kind of routine could be written
where: Word is opened through Automation; then, for each field in each
record, the formatted text is copied to the clipboard; a blank Word doc is
created; clipboard text is pasted into Word; doc is saved as temp.html;
contents of temp.html are imported into new fields for HTML.

Of course, Word HTML has a lot of extra code in it. But what are you gonna
do?

Neil

 

[Tom Wickerath]

Hi Neil,

Of course, Word HTML has a lot of extra code in it.

The HTML output produced by Word is "Fugly", to put it in a term acceptable
for posting! <smile>


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Neil]

There must be some other software out there that converts to HTML and
supports Automation.....