Try using a pass-thru query in Access.  This will force Access to execute the query in SQL Server's terms, not how Access would interpret the query.

Just remember that in Excel, you have a limit of 65,536 rows of data that can be inserted.

As an alternative, you can use pass-through queries in Access.

Depending on the error generated, it is probably an access issue -- the account that the SQL Server agent runs under does not have the proper privileges.  What happens is...

It sounds like you've moved an Access database to SQL Server and now you need to gain access to the data via ODBC and set up a DSN (Data Source...

Check out the following article on http://www.SQLDTS.com

http://www.sqldts.com/?204

From the article...

To transfer local packages directly between servers follow the simple steps below:

1 Create a new package, and add two...

sp_helpuser and sp_helplogins are useful sys sprocs

Nice Tip -- This would be very useful in production processes and make it very easy to track down which specific task failed.

Yes, package logging is nice for troubleshooting.  I normally add this to the DTS package as well as the job (if scheduled).  This will provide start and end times as...

You can execute a DTS package from within an ActiveX Script and then log what the results were of each step (log meaning write to a table).  Then you can...

You can also execute a DTS package from within an ActiveX Script...

Function Main()

'Declare variables

  Dim objPkg

  'Create and...

I just wanted to clarify something with the UNION statement...

As Ganesh has correctly pointed out, using a UNION will automatically remove any duplicate records.  Additionally, if the need ever arises,...

I'm only familiar with DTS.  It is part of SQL Server.  As for Ascential Datastage, never used it.  It sounds like just another ETL tool. Hopefully someone else in the...

Yes, that would be an alternative approach, but I was hoping for more of a point and click solution.  An input box would require the user to type out the...

I've looked at this from within Access to test the CDATE function and it does not like the YYYYMMDD format.  It needs to have something like YYYY/MM/DD with the slashes...