Yes, the syntax of the join inside the query string you execute via OpenSQL must be for the target DBMS - which I guess is not SQL Server...  Some DBMSs...

Definitely the font is the way to go - and you probably won't have the 7 second delay on a simple 290 record report...  We use the font from within...

I've lost the thread of this topic and only read your most recent post....

You could, although it's probably ugly, have SQL Server have a linked server back to your Access...

So when you are logged on as a user to this box (ie, looking at a windows desktop) can you get access to the Unix share?

Could you get a system admin to be the one who creates the procedure (you write the code though) and then the permissions of the code in the proc are...

I also agree..  Insert into a dummy table, then do an update on your main table joining to the dummy table.

You just need outlook configured under the USER account that SQL Server is using...  This needn't be a domain account or involve MS Exchange.  So you can have a local user...

Are both SQL Servers running SP4?

Check permissions - are you using windows auth or SQL Server auth for the linked server?  As suggested, try a simple select without any inserts...

What you should do is check your indices...

Are these the only columns in your table?  How distinct are the values in col3?  For example, you could index based on

col3, then...

Well part of me hopes it works and part now doesn't hahaha - in any case, it sounds like you had a good...

Didn't realise you wanted to execute from a stored proc?  You can run DTS without using a stored proc

Further thread here..

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=131&messageid=262845

Plz don't cross post - we get all messages in all forums in the daily email...  (or at least include links to your other posts so all answers are in...

Ray's correct.  Since you are already doing a check for existance in tblsmall you should ensure that SQL doesn't also do a double check for existance (maintaining referential integrity) in...

It probably means exactly what it says - some string data (probably not binary) would be truncated in the upgrade... .This means that the target column in SQL Server is...