! Boy am I not paying attention while I do this. Thanks again. I'll let you know how THIS works. joel -----Original Message----- From: thelist-admin at lists.evolt.org [mailto:thelist-admin at lists.evolt.org] On Behalf Of darren Sent: Friday, November 23, 2001 3:09 AM To: Joel D Canfield Subject: Re: [thelist] Oledb connection problem with Access XP - renewed On 22 November 2001 at 18:50:03, Joel D Canfield <joel at spinhead.com> wrote: JDC> Hey, look! I can reply to my own post! heh...never a good sign... JDC> Which I'm STILL getting. Any more ideas? not sure what's kicking up the error, but it may be that you're not creating the recordset before the assignment....or are you?? the following code always works for me for sql strings: set objCon = Server.CreateObject ("ADODB.Connection") set objRc = Server.CreateObject ("ADODB.Recordset") objCon.Open objRc.CursorLocation = adUseServer objRc.Open strSQL, objCon, adOpenForwardOnly, , adCmdText if objRc.BOF and objRc.EOF then Response.Write "we got nuffin" else 'get jiggy with the data end if objRc.Close objCon.Close set objRC = nothing set objCon = nothing JDC> Is developing with Access really that much harder than SQL? I've JDC> been working with SQL7/2000 for a year, and it's a dream. Access JDC> continually frustrates me, but it's how this project needs to work. there seem to be a *lot* more quirks when you're coding against access, but for the most part it seems to go fine. memos and blobs can be problematic. but it can't compare to sql2k, that's a *very* nice backend to play with! :> hth, darren --------------------------------------- For unsubscribe and other options, including the Tip Harvester and archive of TheList go to: http://lists.evolt.org Workers of the Web, evolt !