<< CSS and Accomodating different browsers | Home | excluding a dependency via UP2Date >>

Reading memo fields in Access using asp and ado

as a reminder to myself really, in access 2000 there is now a memo field these can only be read once from the ado recordset in asp.  The second time the field will be null, ie if you do the following...

<%= myRS("linkname") %>

<%= myRS("linkname") %>

twice the second one doesnt return anything as it loses the field contents, I believe this is by design

Print | posted on Wednesday, September 28, 2005 3:25 PM

Feedback

# re: Reading memo fields in Access using asp and ado

Left by Tina at 11/15/2005 8:13 PM
Gravatar Thank you! For years I have struggled with this issue. Usually, the server I am working with handles the memo field type just fine. Once in a while, I wind up working with a server that doesn't. Usually, I can just use long text fields. But in one case, today, I could not. Because of your tip, I changed my code so that the first time I look at the memo field in the code, I save its contents to a new variable, then I test for null value. Before, I was checking for null value first, then saving contents to a variable. Thanks to you I now know the importance of order in this situation. Thanks again!

# re: Reading memo fields in Access using asp and ado

Left by Mike Landers at 1/10/2006 10:29 AM
Gravatar (Just passing through, found this on a Google search having hit the same problem.)

Your solution works, but the "real" solution is to put the memo field at the end of the SELECT query. So if you have a memo field somewhere in the middle of your column structure, you need to rearrange the field order in the SELECT and not use 'SELECT * FROM'

Your comment:





 
Please add 1 and 6 and type the answer here:

Disclaimer: Paul Farrow is not responsble for any damage, direct or indirect,
caused by the use of the information on this site. Use at your own risk.

Design by Bartosz Brzezinski

Design by Phil Haack Based On A Design By Bartosz Brzezinski