AppendChunk and SQL 2012

I had a previous question on Experts exchange.  Here  In that solution, I arrived at the notion that using AppendChunk would help me load data into SQL.  I was told by one of our programmers that using AppendChunk with later versions of SQL does not work.  Is anyone familiar with this method in VB6 and what versions this works with in SQL...if there really is any limitations?

We are currently utilizaing SQL 2012 and I know we have not tried it yet, but perhaps I may ask first to see if one of the experts here knows if there is a limitation.
al4629740Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Familiar with the method and I can't think of any reason it would not work with a later version of SQL.

What exactly is the problem?   Do you get any kind of error message?  Also, are you using a different version of Access as well?  If so, what version and is it O365 or a traditional perpetual install?

Jim.
0
al4629740Author Commented:
No error message that I know of other than that's what I was told.... I wish I could tell you more.  Have you tried using this method with SQL 2012?
0
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<Have you tried using this method with SQL 2012?>>

 No I have not.  Append/Get Chunk is not something that is used all that often.  However as I said, I can't think of any reason why it would not work.  The following:

https://support.microsoft.com/en-us/help/194975/how-to-read-and-write-blobs-using-getchunk-and-appendchunk

  is something you may want to pass along lacking specifics on the problem.    Make sure they look at the "Notes" section at the bottom, as it lays out some of the issues that might be encountered.

  At a guess, it would have more to do with the driver being used than anything.  Nothing has changed in SQL Server 2012 in regards to field types that I'm aware of.

  But without more details, that's just a guess.

Jim.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SQL

From novice to tech pro — start learning today.