The quick search is just setup using Epicor's "Quick Search Entry". Nothing special. Does the "Check you where clause" not apply in that case?
--- In vantage@yahoogroups.com, John Driggers <waffqle@...> wrote:
>
> Check your where clause. If I recall correctly, they are the most common
> culprit. Are you calling the search through code or just setting it up
> somewhere via the 'normal' methods?
>
> On Mon, Apr 23, 2012 at 5:08 PM, Anon <jgiese@...>wrote:
>
> > **
> >
> >
> > I was unable to find any resolved information regarding this type of
> > error. Any chance there is one thing in particular that causes it in
> > relation to Quick Searches?
> >
> > Error Detail
> > ============
> > Failed to enable constraints. One or more rows contain values violating
> > non-null, unique, or foreign-key constraints.
> >
> > Stack Trace
> > ===========
> > at System.Data.DataSet.FailedEnableConstraints()
> > at System.Data.DataSet.EnableConstraints()
> > at System.Data.DataSet.set_EnforceConstraints(Boolean value)
> > at System.Data.DataSet.RejectChanges()
> > at Epicor.Mfg.Diagnostics.DataTracer.WritePacket(TracePacket packet)
> > at Epicor.Mfg.Proxy.QuickSearchImpl.RunQuickSearchPaged(QuickSearchDataSet
> > ds, Int32 piPageSize, Boolean& pbMorePage)
> > at
> > Epicor.Mfg.UI.Adapters.QuickSearchAdapter.RunQuickSearchPaged(QuickSearchDataSet
> > ds, Int32 piPageSize, Boolean& pbMorePage)
> >
> >
> >
>
>
>
> --
> *John Driggers*
> *High End Dev, System Design, Profit Drinking*
> *
> **:: 904.404.9233*
> *:: waffqle@...*
> *:: NO FAXES*
>
> *
>
> *
>
>
> [Non-text portions of this message have been removed]
>