Could not allocate ancillary table for view resolution

anonymous_at_discussions.microsoft.com
Date: 05/01/04

  • Next message: Steve Kass: "Re: Could not allocate ancillary table for view resolution" 
    Date: Sat, 1 May 2004 11:01:04 -0700

    >-----Original Message-----
    >I am receiving this error when running a query:
    >
    >Server: Msg 4414, Level 16, State 1, Line 1
    >Could not allocate ancillary table for view resolution.
    >The maximum number of tables in a query (256) was
    >exceeded.
    >
    >I have found the error in the knowledge base but only for
    >SQL Server 2000, we are still using SQL Server 7.0. It
    >was running fine about 3 weeks ago; I hadn't made any
    >changes to the query, and suddenly this happened. I have
    >already rebooted the server. Does anyone know where this
    >message could be coming from or how to fix it?
    >
    >Thank you,
    >Sassgirl
    >.
    >

  • Next message: Steve Kass: "Re: Could not allocate ancillary table for view resolution"

    Relevant Pages

    • Re: search field and table name change required
      ... Thanks for your query. ... the receiving qty and halves the shipped qty and calculates qoh. ... SIN_ITEM_NO SUMOFUNITS RECEIVED SUMOFUNITS USED QOH ...
      (microsoft.public.access.formscoding)
    • Re: search field and table name change required
      ... Thanks for your query. ... When there are more that 2 or more transaction for the item than it doubles ... the receiving qty and halves the shipped qty and calculates qoh. ... SIN_ITEM_NO SUMOFUNITS RECEIVED SUMOFUNITS USED QOH ...
      (microsoft.public.access.formscoding)
    • Re: search field and table name change required
      ... Thanks for your query. ... the receiving qty and halves the shipped qty and calculates qoh. ... SIN_ITEM_NO SUMOFUNITS RECEIVED SUMOFUNITS USED QOH ...
      (microsoft.public.access.formscoding)
    • Importing a .DBF file
      ... I'm receiving the following error message: ... Query must have at least one destination ...
      (microsoft.public.access.externaldata)
    • Re: Hide the Next Button
      ... the entire query rather than just the filtered version. ... And for whatever reason the recordcount I ... was receiving was actually for the larger query and not the filtered ... with large volumes so I stuck with this rather than debugging why the ...
      (microsoft.public.access.formscoding)