Sharepoint Query comes with font descriptions on some fields

I am linking to a simple SharePoint list. The field shows fine in
SharePoint, but in Access 2003, the field has code like this:
In Sharepoint, the field is "my text from sharepoint"
In access it shows up as
font color=black"my text from sharepoint"/font
How can I strip the font information? I need to do this for a number
of entries.

"elbyc" wrote in message
...
I am linking to a simple SharePoint list. The field shows fine in
SharePoint, but in Access 2003, the field has code like this:
In Sharepoint, the field is "my text from sharepoint"
In access it shows up as
font color=black"my text from sharepoint"/font
How can I strip the font information? I need to do this for a number
of entries.

Was the data edited with access 2007, or some other application?

Remember, in access 2007, we have support for rich text fields. This opens
up a lot new possible features for ms-access (such as having memo fields
with nice formatted text (colors, fonts, graphics). So, you can make killer
help and note pages or product descriptions in access 2007 since controls
now support rich text....

We don't have that support in access 2003...

So, it really depends on where that column/data came from...but a lot of
applications such as access 2007, or OneNote etc has support for rich
text....

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada

Perhaps that's the problem. SharePoint is 2007, Access is 2003. Does
that mean I need to do a substitution query for all of that formatting
information?

"elbyc" wrote in message
...
Perhaps that's the problem. SharePoint is 2007, Access is 2003. Does
that mean I need to do a substitution query for all of that formatting
information?

Well, the problem here is where this data is coming from?

That markup text is likely coming from other applications or software is
using that SharePoint list and is saving/using rich text.

Access 2007 as mentioned does allow the use of rich text (markup text) in
memo fields.

Are there 2007 access users ALSO editing this list? If there is, then ensure
that rich text is disabled for those text boxes in 2007.

You likely are seeing text like:

divfont color=redstrongThis is bold red text/strong/font/div

The above will display text as being bold, and red in access 2007. In 2003
you see the markup text, not the red and bold text.

If NO other applications are using that data, then you should be able to
just store text.

Perhaps some other web based applications is using that "list" on SharePoint
that has the ability to save/store text with markup language as you are
seeing.

You have to find out who/what/when the other applications are that are
storing this data.

This is not due to it being SharePoint 2007 and access 2003, that markup
text data is in there due to something else editing that data and being
allowed to store rich text.

You really should try to find out what other application is storing that
text. If there none, then you certainly work towards removing that extra
markup stuff.

In access 2007, you can use the plainText function. This function will strip
out the rich text formatting (remove those markup tags). So, if you have any
users of 2007, then you likely can quite ease fix this problem.

Un converting this mess may be quite difficult in 2003. At any rate, you
have to find out why and where this data is coming from. You can't just
throw it out.

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada

On Jul 8, 5:16*pm, "Albert D. Kallal"
wrote:
"elbyc" wrote in message

...

Perhaps that's the problem. SharePoint is 2007, Access is 2003. Does
that mean I need to do a substitution query for all of that formatting
information?

Well, the problem here is where this data is coming from?

That markup text is likely coming from other applications or software is
using that SharePoint list and is saving/using rich text.

Access 2007 as mentioned does allow the use of rich text (markup text) in
memo fields.

Are there 2007 access users ALSO editing this list? If there is, then ensure
that rich text is disabled for those text boxes in 2007.

You likely are seeing text like:

divfont color=redstrongThis is bold red text/strong/font/div

The above will display text as being bold, and red in access 2007. In 2003
you see the markup text, not the red and bold text.

If NO other applications are using that data, then you should be able to
just store text.

Perhaps some other web based applications is using that "list" on SharePoint
that has the ability to save/store text with markup language as you are
seeing.

You have to find out who/what/when the other applications are that are
storing this data.

This is not due to it being SharePoint 2007 and access 2003, that markup
text data is in there due to something else editing that data and being
allowed to store rich text.

You really should try to find out what other application is storing that
text. If there none, then you certainly work towards removing that extra
markup stuff.

In access 2007, you can use the plainText function. This function will strip
out the rich text formatting (remove those markup tags). So, if you have any
users of 2007, then you likely can quite ease fix this problem.

Un converting this mess may be quite difficult in 2003. At any rate, you
have to find out why and where this data is coming from. You can't just
throw it out.

--
Albert D. Kallal * *(Access MVP)
Edmonton, Alberta Canada


Thanks for the interesting response.

I created the list from an Excel 2003 file I got from another user. It
is possible but not likely that the original file was in a higher
version of Excel. I imported it into Access 2003 using Import (not
link). Then I imported it into SharePoint using the custom list from
spreadsheet function. Then I linked it from Access and it showed up
with that coding. I will see if one of my colleagues has a higher
version of Access that can strip the formatting for me, but I am
certain no one else has been using these tables and lists but me.

If you're wondering why I didn't just import the spreadsheet directly
from Excel into SharePoint, I had some problems when I tried to do
that, and had a cleaner file when I used Access as an intermediary.