Ok, I solved the problem myself. 🙂 I had to do a lot of creative googling but I finally figured it out...

I had to create a dummy table exactly...

Wouldn't it just be easier to make a user function or a reference table?

I actually tried doing that with the path and forcing SQL Server to use the 32 bit drivers...but no go.

We actually ended up scrapping the concept. Our client was...

Thanks for the reply... all the research I've been looking at has pointed to Sybase not developing a 64 bit driver and that people were having all kinds of problems...

Hmm ok, nobody has an experience with trying to connect to sybase from sql server? 🙂

I kinda solved the problem... but not ideally...

I found an article online about how...

Any insight at all would be super helpful. 🙂

Woot thanks! With some trial and error it finally went in!!!

Ok, so I just looked in the advanced tab... it says the column widths are all 50...

So, are you saying I need to change the column widths here in...

It runs on the remote server. Its a java app. I believe I figured out the problem though... its because sql is running under "localsystem" and it doesn't...

Wow, that post is so old! I can't remember what the problem was originally related to...but I believe I had to reinstall it. 🙂

Its ok. 🙂

shouldn't he make his own post instead of hijacking mine? lol

I haven't been able to fix this error either... I had to make a work around by creating a DTS...

I don't think that's what it is as it does the same thing if I put the database on the c drive of the server.

Also it has nothing to do...

well how do I know what dll it can't find?

Is there some listing that deliniates what dll files get accessed when an SSIS package needs to be created?

Hmm.. I don't think it is related to that... 🙁

I have also ran the DLL registration command line on my client pc and on the server for DTS.dll and...