Well, I gave these approaches a try, including moving cmd.exe to a new folder and setting that folder up in the path.  No luck there, as, interestingly enough, Windows appears...

The code is a simple call to PKZip... I have it at work, but basically it is the following:

Job Step Code:

c:\Program Files\PKWare\PKZip.exe -add -move  \\Server\Share\Folder\Zipfile.zip @\\Server\Share\Folder\FileList.lst

The file \\Server\Share\Folder\FileList.lst...

Nope, PKZip is what is being called from inside the "Operating System Command" type Job Step.  That is the problem.

The problem we have is not that simple, unfortunately.  Perhaps a bit more background is in order...

We use PKZip to move files into a zipfile before they get sent out. ...

Consider this approach...

Three tables with an identity field for each table.

When you add an invoice, add a record to the invoice table, then use the identity from the invoive table...

If you are having problems running it from the stored profcedure, but you can run it fine from Query Analyzer, check to see what account your service is logging in...

If you are summing, then you are already using a GROUP BY clause. To limit the results to only certain dates, you can use the HAVING clause:

SELECT fullName,

...

Add the table in with a LEFT JOIN and use the B2BError.Warning = 2 in the ON instead of the WHERE clause:

SELECT Customers.EntKey,

...

One other thing that I found useful is to add a header to stored procedures...

/******************************************

** Procedure: {Proc_Name}

**

** Notes: {describe the use of the procedure}

**

** Author: {AKA: Who to talk to...

The problem that you have with using a Global Temp table (##) is that you get back into the permission problem that you are trying to solve in the first...

True, a delete and a DBCC CHECKIDENT (@table_name, RESEED, @id) will do the same thing, but it could potentially take a great deal more time (due to the logging nature...

Remember, when using Temp tables, sometimes it is better to use a master calling procedure that creates the temp table. FOr example, if you are using a Global Temp...

One rule of thumb I like to use as well is to use a Temp table if the information is going to be used more than once. If it...