[dba-SQLServer] Re: Update query through Access ADP

Steve Erbach erbachs at gmail.com
Fri Mar 11 07:58:13 CST 2005


Dear Group,

I went ahead and used Query Analyzer to do the job for me. I'm just
curious what it is about my Access ADP that stopped the UPDATE after
only 10,000 rows?

Steve Erbach


On Fri, 11 Mar 2005 07:51:53 -0600, Steve Erbach <erbachs at gmail.com> wrote:
> Dear Group,
> 
> I've been looking through some of a client's ASP application with a
> view to making some slight modifications. (There are almost 800 ASP
> files. Yikes!)
> 
> The back end is SQL Server and I've been using Access 2003 to
> construct views and stored procedures. I've been working on a COPY of
> the tables on my own SQL Server rather than the customer's live data.
> 
> What's got me curious is this: I've been working with an sproc that
> updates a column containing an email address. It looks something like
> this:
> 
> UPDATE Projects2
> SET ContactEmail = NULL
> WHERE (Contact = '') OR (Contact = ' ') OR (Contact IS NULL)
> 
> So if the Contact name doesn't have anything in it, I want the
> Contact's email address to be NULL. At present, there's a default
> e-mail address in every row.
> 
> After the sproc runs I look at the table itself. Well, this table has
> 133,000 records in it. Access 2003 shows me the first 10,000 by
> default. But when I go past the 10,000th record, the e-mail column
> still has addresses in it even though the Contact field is empty.
> 
> Is there something I'm missing in the sproc? Something like a command
> that says, "OK, I really, REALLY want to update the rows beyond
> 10,000, too."
> 
> Regards,
> 
> Steve Erbach
> Scientific Marketing
> Neenah, WI
> www.swerbach.com
> Security Page: www.swerbach.com/security
> 


-- 
Regards,

Steve Erbach
Scientific Marketing
Neenah, WI
www.swerbach.com
Security Page: www.swerbach.com/security



More information about the dba-SQLServer mailing list