Re: MSDataShape (MDAC 2.8) limitation on the query length

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Brannon Jones [MS] (branjo_at_nospam.microsoft.com)
Date: 03/24/04

  • Next message: JS: "BatchOptimistic Locking" 
    Date: Tue, 23 Mar 2004 16:59:26 -0800

    The fix was released to Product Support today. You can contact Product
    Support and reference KB# 838405. The KB article should be posted to
    microsoft.com within a few days. The link will be:
    http://support.microsoft.com/?id=838405. That link wont work until the
    article is posted.

    Let me know if you have any questions. 

    -- 
Brannon Jones
Developer - MDAC
This posting is provided "as is" with no warranties and confers no rights.
"TWiSTeD ViBE" <twisted_vibeNO@FKINSPAMyahoo.com> wrote in message
news:c3p01s$gf5$1@kermit.esat.net...
Have you any idea how long i'll have to wait until this patch is available?
Rob
  "Brannon Jones [MS]" <branjo@nospam.microsoft.com> wrote in message
news:OZU9vggDEHA.3348@TK2MSFTNGP11.phx.gbl...
  We are working on a fix for this.  I will post details to the group when
  it's ready.
  Thanks!
  -- 
  Brannon Jones
  Developer - MDAC
  This posting is provided "as is" with no warranties and confers no rights.
  "TWiSTeD ViBE" <twisted_vibeNO@FKINSPAMyahoo.com> wrote in message
  news:c3f63k$9h6$1@kermit.esat.net...
  > Hi,
  >
  > (I'm quoting this from elsewhere but here is my problem)
  >
  > ----------------------------------------------------
  > "With MSDataShape shipped with MDAC 2.8, there is a new
  > limitation on the query length we can supply to the Open()
  > method of a recordset. In fact, the hierarchical query
  > must not be longer than 32768 characters. If you supply
  > more than that, then you'll have the error:
  >
  > "Argument passed to the Data Shaping Service was invalid".
  > ----------------------------------------------------
  >
  > My query is far larger and is required to be - is there any way around
  this
  > limitation?
  >
  > Rob
  >
  >
  • Next message: JS: "BatchOptimistic Locking"

    Relevant Pages

    • Re: MSDataShape (MDAC 2.8) limitation on the query length
      ... The fix was released to Product Support today. ... Developer - MDAC ... In fact, the hierarchical query ...
      (microsoft.public.sqlserver.odbc)
    • Re: MDAC memory leak hotfix
      ... No there's no where else to get the fix. ... Call product support to obtain the free hotfix. ... Another thing is that it says to call Product Support to obtain the hotfix. ... And will it work on MDAC ...
      (microsoft.public.data.ado)
    • RE: 6gw1u4iu
      ... We provided a fix for you that will be available in IDW14. ... SQL Server Data Mining ... OLEDB source (with the DMX prection query) and throw the result into a SQL ... the package fails with the error in the attached ...
      (microsoft.public.sqlserver.datamining)
    • Re: Strange Prediction behavior
      ... We provided a fix for you that will be available in IDW14. ... SQL Server Data Mining ... OLEDB source (with the DMX prection query) and throw the result into a SQL ... the package fails with the error in the attached ...
      (microsoft.public.sqlserver.datamining)
    • Re: Reporting problem
      ... There is no fix for this, except to update each query. ... Does MS have a fix that I can apply to fix the rest of the queries? ... have 2 SMS environments and I would like to get all the queries to work. ... Some are fine and these are all the standard reports. ...
      (microsoft.public.sms.admin)