[AccessD] UNION slowness

Nope, but it may just be a SQL Server issue.  I am having SQL Server issues right now.

John W. Colby
www.ColbyConsulting.com


Drew Wutka wrote:
> Did this fix the problem for you JWC?  If not, it sounds like this is in
> Access, make sure that your SQL is SQL Server friendly, so it's
> passthrough.  Otherwise Access is going to want to work on the data.
> 
> Drew
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
> Sent: Monday, March 15, 2010 10:02 AM
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] UNION slowness
> 
> Hi John
> 
> How about using UNION ALL? Without the ALL it performs a default
> DISTINCT which may be very slow.
> 
> /gustav
> 
> 
>>>> jwcolby at colbyconsulting.com 15-03-2010 15:51 >>>
> I have always done a UNION to get a combo list with *; All as the first
> item in a combo of other 
> items.  PKID, Client or PKID, Product etc.
> 
> These unions are takling as looooooong time (many seconds) when going
> against a SQL database.  Not 
> sure why because the actual data itself is almost instant, it is just
> when unioned with my other 
> piece it takes forever to get the result set.  Strange.
> 
> I could do a custom callback but it takes me forever to figure out the
> callback crap, and I just 
> generally hate them.
> 
> I wanted to do a value list since the lists are short, but AFAICT the
> list value function has to be 
> interpreted and dumped in to the property in OnEnter and the like.
> Clumsey, particularly when one 
> combo depends on (is filtered by) another list (products filtered by
> client etc).
> 
> Any words of wisdom on this?  Something I have forgotten or never knew?
>