Actually this is being done from ACCESS2000. The variable just before the table update from ACCESS shows me the right text with all the characters.

I also just copied and pasted  the...

noeld, I just got new data and tested with the changed registry values. The process did not timeout, and ran successfully. Thanku very much for your suggestion.

noeld, thanku very much for your suggestion. I have made the registry changes and the data will be coming in next week for me to test it on. It will...

That was very careless of me. Thanku, that worked.

1. There is only one record inserted at any time.  It is a small table updated once with one record in a month or so.

2. fld2 cannot have null values.

3....

jhouston, thanku for your time and patience in explaining this to me. I will try this and post my results.

Actually I am not sure if it is ADO or DAO. I have taken over this code and am relatively new to access.  The problem code is as follows

Call DoCmd.TransferDatabase(acExport,...

Thanku, that worked very well and it is  more easy to read the job step too !

Do you have any suggestion of how i can implement this package as a job step without using GUID, and the package being a local package  ?? Any thoughts would...

Just made it work ! The reason for the error was because my file pointed to a location in my hard drive and the server was looking at its own hard...

Well, I am running this job as administrator, so I might have the permission. While viewing the job history, it tell me that it failed since it did not find the...

Probably what Greg Charles and diogenes0412 have suggested will generate the same kind of code.  I did try  one method - to paste the code as suggested from the scheduled...

Acually I do not want to run it from windows or dos prompt.

is there anyway i can do it as a SQL server agent job-job step, since this has to...

I am using dynamic SQL, that is why I cannot change the variable as you have  done for @DATA.

But QUOTENAME worked great ! Thanku.

This works fine from Query Analyzer but in my Stored procedure it still gives the same error as before. I think the EXEC does not recognize the  "set quoted_identifier off"...