Hi,
I have Access getting imap emails for me via Chilkat ActiveX
basically I get the html email body OK & generally looks fine for normal email.
However I get SMS/text messages via a online service and they have a rather fancy format with columns.
Looks nice in email cilents & any other html viewer but when I receive into my database it keeps colours & bold etc but no columns so actually makes it very difficult to view.
I think it is the ' td colspan="2" ' etc than gets lost
Do you know if MsAccess (365) should be able to cope with colspan.
I could search/replace but not sure what to put in its place, a New Line would not help much as 3 columns wide actually splits the data.
I know very vague but hoped someone might be able to start me get me started in the right direction. I did wonder if UTF-8 & iso-8859-1 could be a issue but not sure makes any difference with the editing. I think generally I use UTF-8 to send but looking below lots on incoming seem to use iso-8859.
e.g.
<html><head><META http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
</head><body>
<table width="100%" border="0" cellspacing="5" cellpadding="0">
<tr>
<td colspan="2"><font face='Arial, Helvetica, sans-serif'><b><font color='#000000'>You have a new<i><font color="#FF0000"> </font></i>message.<br>
I have Access getting imap emails for me via Chilkat ActiveX
basically I get the html email body OK & generally looks fine for normal email.
However I get SMS/text messages via a online service and they have a rather fancy format with columns.
Looks nice in email cilents & any other html viewer but when I receive into my database it keeps colours & bold etc but no columns so actually makes it very difficult to view.
I think it is the ' td colspan="2" ' etc than gets lost
Do you know if MsAccess (365) should be able to cope with colspan.
I could search/replace but not sure what to put in its place, a New Line would not help much as 3 columns wide actually splits the data.
I know very vague but hoped someone might be able to start me get me started in the right direction. I did wonder if UTF-8 & iso-8859-1 could be a issue but not sure makes any difference with the editing. I think generally I use UTF-8 to send but looking below lots on incoming seem to use iso-8859.
e.g.
<html><head><META http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
</head><body>
<table width="100%" border="0" cellspacing="5" cellpadding="0">
<tr>
<td colspan="2"><font face='Arial, Helvetica, sans-serif'><b><font color='#000000'>You have a new<i><font color="#FF0000"> </font></i>message.<br>