Check the MDAC versions on the two machines.  It's the brains behind Access' data access. 

Is it possible to pre-process the results of the grouped subqueries into separate tables?

Doing aggregate functions on derived tables (themselves having aggregate functions) is implicitly going to be very costly,...

Since you're deleting everything and "starting over", you might care to:

• make sure your recovery model is on "simple" on the DB being rebuilt from scratch.  That's a LOT of stuff...

For what it's worth - not wanting DTS "because it would be called from .NET" isn't a good reason.  DTS packages can easily be called from .NET, and with some...

well - you could always "split the difference", and split the work into two separate pieces (perhaps - don't know what exactly you're doing).  Such as - get the ASP.NET...

Yikes.  Have you considered switching from the linked servers to a OPENDATASOURCE or OPENROWSET syntax?  It's functionally the same as building a throwaway, one-time linked server.  That way - you can...

Careful now - that's a different TRUNCATE.  the log files "truncate" <> TRUNCATE TABLE.  That's a evil twin

TRUNCATE TABLE <table1> is a T-SQL equivalent...

By the way - for better or for worse - Although I can see why you'd want to do this - having the whereclause be something getting passed in sets...

the issue is the @where clause

@whereclause='tbldogs.dogcode=''LAB'''

what's in the @whereclause?

Also, if you can pull it off - drop any and all indexes you can during the delete process, then recreate them when you're done.  things will run quite a...

I didn't notice the simply mode.  That being said - simple recovery is essentially a "self-truncating" process.  It will log transactions for the length of time they are open/un-committed, and...

There's something wrong with this story.  Ever since I first read it - I've been calling their customer service continuously, and I still haven't received my letter yet.    If you...

Assuming I understand what you're doing - have you considered doing away with using the function at all?

use something like

....

case when (@status like '%,'+s.value+'%') or (@status like s.value+',%') then...

Actually - you can often enough help yourself by getting your log files to a certain size, and backup and truncating the committed transactions, but NOT shrinking the files.  Especially...