Have you verified that the job exists on the other server and that you don't have a typo??

I think in this particular instance that it is by design.  The reason I think this is you are performing a computed calculation but to be able to perform that...

Hans,

I would install Win2K only if the final place where the database will be running is Win2K.  As far as detaching from SQL2K to SQL7 system make sure that...

I would try putting single quotes around your date/time.  The system is probably interpreting your statement mathematically and not recognizing it as a date/time.

Easiest way to learn about MS-Access joins is to open up Access and create a query.  Place both tables in the query and then from either table (I prefer the...

http://support.microsoft.com/gp/lifeprods

Chili,

I would research UNION in BOL (books online).  This will probably help you.

Dragan,

I would check and ensure that whomever is set to be the "run as" has permissions to get to the directory where the file lives.  If this is running...

If the only thing that is changing is the filename why not create a single DTS package that is called from all the others that does the checking?  This way...

You can review CROSS JOIN

CREATE TABLE #test

(Field1 CHAR(1),

 Field2 VARCHAR(50)) ON [PRIMARY]

INSERT INTO #test VALUES ('A', 'A1')

INSERT INTO #test VALUES ('B', 'B2')

INSERT INTO #test VALUES ('C', 'C3')

INSERT INTO #test VALUES ('D',...

David,

Yes.  I believe it has already been released as part of the Beta program for 2K5.  Currently the MSDE exists but comes without QA to interface with it.  I...

You could do this by calling a sp that dynamically builds CREATE DATABASE @DBName and then is EXEC via sp_executesql.

I would review the views that were created in Oracle and ensure that the SQL data types match the Oracle.  It may be some data-type conversion truncation issue.

If you have an ID of some sort on the table you could do WHERE RecordID BETWEEN 201 AND 300

I dont think you can, and I dont think it will affect performance either way.  Table variables (unless they get large) reside in memory and are always for the scope...