It might make a difference what you are using to consume the output of the stored procedures. For example in Access vba, there is an ADO NextRecordset method that allows...

Since you seem to be stuck with the date in a non-date format...

What if you had your where statement like this:

WHERE 20070801 > StartDate

AND (20070801 <= EndDate or EndDate...

Use a Conditional Split tool to check to see if a field is null. You can direct those records with null fields down another path that will let you fix...

Now that I think about it, that is true. That is probably why I generally sum to a temp table and then update from there.

I was going to suggest that also. But I had tried it with the WHERE clauses and it worked.

Code is much easier to read, in my opinion, using joins rather...

I was able to use this SQL and it ran as is. I created a test table in Northwind and updated it from Order Details using the orderID and the...

MS did, and does, provide, in Access, a way to have a full and tight integration with SQL Server, which enables you to use the user friendly, GUI Access as a...

There are actually quite a few "tranformation" tools that you can use in SSIS. You could use a conditional split to send those items that have an incorrect date down...

One way to run an SSIS package from T-SQL is to set it up as a job and then start that job in TSQL. Assuming you have a job "Weekly...

Another alternate solution might be to use SQL security. You could set the users up one time with SQL logins, set them up as users with the appropriate security in...

I agree, you should CREATE the temp table. Also, it should not be prefaced with @ since that is reserved for variables. A temp table should be prefaced with #...

Also, as Steve mentioned above, using an adp instead of an mdb, moves the tables to SQL server. You can then use stored procedures as the data source to further...

Since he is using an adp, you do not have to set a connection, like you do when you use an mdb. An access adp maintains its own connection to...

Ah , the not looking back part! Yes, I will follow up elsewhere. Thank you.

In the original article Andy posted the following:

Let's start with a common example. If I asked you which is the best practice, using Windows authentication or SQL logins, I bet...