Tabs in Memo Field (driving me crazy)

[tom]

Hello,

I have a table with a memo field that has some TAB characters inside
it. When viewing the contents of this table (simply by double-clicking
the table in the database window to bring up a datasheet), Access
really makes a mess of things by trying to display a Tab character,
which it doesn't do quite right, making the text VERY HARD to edit.

This behavior happens on my machine, but not on my co-workers'
machines. Instead, they see a LITTLE BOX where the Tab character is.
Very handy. We are all running Win XP pro and Access 2002 (and using
Arial as our datasheet font). Argh.

Any ideas?

-Tom

 

[Allen Browne]

Access doesn't really support embedded tabs in a Text or Memo field.

Would you prefer to replace the tab characters with (say) 4 spaces? If so:

1. Create a query into this table.

2. Change it to an Update query (Update on Query menu).

3. Drag the memo field into the grid.

4. In the Update row under the MyMemo field, enter:
Replace([MyMemo], Chr(9), " ")

5. Run the query.

 

[tom]

Allen-
What do you mean it doesn't "support" them? I imagine they will stay
around in my data without trouble... I solved the problem by making a
little widget that breaks the contents of the field into separate
textboxes for editing and then puts them all back together for
storage.

-Tom

Access doesn't really support embedded tabs in a Text or Memo field.

Would you prefer to replace the tab characters with (say) 4 spaces? If so:

1. Create a query into this table.

2. Change it to an Update query (Update on Query menu).

3. Drag the memo field into the grid.

4. In the Update row under the MyMemo field, enter:
Replace([MyMemo], Chr(9), " ")

5. Run the query.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Hello,

I have a table with a memo field that has some TAB characters inside
it. When viewing the contents of this table (simply by double-clicking
the table in the database window to bring up a datasheet), Access
really makes a mess of things by trying to display a Tab character,
which it doesn't do quite right, making the text VERY HARD to edit.

This behavior happens on my machine, but not on my co-workers'
machines. Instead, they see a LITTLE BOX where the Tab character is.
Very handy. We are all running Win XP pro and Access 2002 (and using
Arial as our datasheet font). Argh.

Any ideas?

-Tom

 

[Allen Browne]

Right: you can store most things in a memo field, but if you want to go to
the trouble of parsing it, you may be interested in Stephen Lebans' Rich
Text:
http://www.lebans.com/richtext.htm

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Allen-
What do you mean it doesn't "support" them? I imagine they will stay
around in my data without trouble... I solved the problem by making a
little widget that breaks the contents of the field into separate
textboxes for editing and then puts them all back together for
storage.

-Tom

"Allen Browne" <[email protected]> wrote in message

Access doesn't really support embedded tabs in a Text or Memo field.

Would you prefer to replace the tab characters with (say) 4 spaces? If so:

1. Create a query into this table.

2. Change it to an Update query (Update on Query menu).

3. Drag the memo field into the grid.

4. In the Update row under the MyMemo field, enter:
Replace([MyMemo], Chr(9), " ")

5. Run the query.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Hello,

I have a table with a memo field that has some TAB characters inside
it. When viewing the contents of this table (simply by double-clicking
the table in the database window to bring up a datasheet), Access
really makes a mess of things by trying to display a Tab character,
which it doesn't do quite right, making the text VERY HARD to edit.

This behavior happens on my machine, but not on my co-workers'
machines. Instead, they see a LITTLE BOX where the Tab character is.
Very handy. We are all running Win XP pro and Access 2002 (and using
Arial as our datasheet font). Argh.

Any ideas?

-Tom