If you are using SQL Server 2000

This is a great shortcut:

DECLARE @i varbinary(20)

SET @i = 0x00000E0000120002

SELECT master.dbo.fn_varbintohexstr(@i)

I believe Julie is Right. You need to save the package through the Package (or Package2) object and Use the SaveMethod and to gain access to the object from SQL...

Phill,

I have THE SAME Problem than you but with another proprietary legacy db.

1. I do The Datapump step and the ODBC Driver speed is KEY

2. I have 2 sets of staging...

Let me put this Plain and Simple, a SysAdmin CAN'T Be prevented from changing the Data. Period

sysadmins are the DB GODS if you want to have an analogy!

The reason is...

If you look at the Table definition and the Column is a "Flag", After the statement is run there is no way to tell if the statement used to modify...

Make sure you qualify the owner on the on the record source!

eg: instead of Tblame use dbo.TblName

HTH

Adding to that you can:

1. Put your Routines in the Model and every time you create a newDB you will get your stuff Automatically.

2. If you are getting into consulting...

The answer "The update statement will run but it will not update all the columns as expected"

IS WRONG!!!

1. It Will update Both Columns!

2. And it is as expected...

Just a way!!

1. create a linked server

2. use a SQL Task to create a STAGING Table with your query

3. use that staging table as the source of your DDQ

several options here:

the Best is to use STAGING TABLES

you could also change the TRUNCATE to DELETE and wrap all in one transaction. at the end if no rows are avail...

I have no clue.

I didn't post the question

What happened in this case is that Access is Smart Enough to convert True to 1 when sending the query to sql server

The problem is that the SQL CAN'T BE CHANGED

If you don't want to make it Global and I still don't know what's your problem with that?

You can

1.Create A SYSTEM DSN pointing to...

Test as bit