On 3 Jan, 00:06, "Albert D. Kallal" <PleaseNOOOsPAMmkal... (AT) msn (DOT) com>
wrote:
I guess I misunderstood

"So, remove the sql from the combo box, build a view..and link the
combo box direct to that view (JUST USE the view name...the sort, and
any sql need to be in the view). The result is quite good combo box
load performance. (and again, not very much work. "

There was a crossover from Access to SQL and I followed the wrong path
when reading this!

Jon

"J-P-W" <jonpwebb (AT) gmail (DOT) com> wrote

guess I misunderstood

any sql need to be in the view). The result is quite good combo box
load performance. (and again, not very much work. "

There was a crossover from Access to SQL and I followed the wrong path
when reading this!

Jon

--------

Not a problem. My tone was perhaps too harsh (my sorry, my apology).

However, when it comes to my advice "sending you down" the wrong path I have
to respond a bit harder. The reason here is then it is MY FAULT and my
advice is being miss-understood. In other words, it really important for me
to have followed up here. I don't want to waste YOUR valuable time. I have
to TAKE responsibility for my advice given, so I responded with strong tone.

So, anyway, yes, that advice was SPECIFIC to sql server. The suggestion is
to not use sql to a LOCAL linked table which in turn is then linked to sql
server. The "extra" step that jet has to go through causes extra network
chatter. The sql in the combo box has to be parsed, and it causes some
network load. So, using sql that points to a linked tables causes a SLIGHT
delay in time. So, the suggesting is to use NO sql, and NO using of a local
saved query. In other words, eliminate ALL local sql. That means for the
combo box you place ONLY the name of the linked table. This means if you
need sorting, or 2 columns, then you be forced to use a view on the sql
server side, and then link to that view, and then specify ONLY the view
name. eg:

cboViewFormCust

So this "suggestion" is just a trick to remove some delay and eliminate the
network clatter that JET does when you use local sql linked to sql server.
This is not a huge delay. I find it likely not worth the time for forms with
only 1 or 2 combo boxes. However, if you have more then 1 or 2 combo boxes
on a form linked to sql server, then this work pays off. It just another tip
to make the form run a bit more snappy. I find this view suggestion somewhat
less work then building a pass-through query and then basing the combo box
on that pass-thought query. Using an pass-though query is even better
suggestion, but tends to be MORE work then building views server side and
linking them. This is the delicate balance between more work, and more
performance. You can hand code reocrdsets for every combo box, but then the
cost of deveopument goes up too high. So, I find a good compromise and the
least amout of work is to remove the sql and use sql server views. So, no
local sql, no local query, and just use a sql server view. You thus link to
the sql view (it will appear as an linked table). I suppose for some a
pass-though query is not that much more work.


-
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal (AT) msn (DOT) com

On 3 Jan, 02:03, "Albert D. Kallal" <PleaseNOOOsPAMmkal... (AT) msn (DOT) com>
wrote:
Albert,

Harshness excused! No problems. Having not used SQL server before I
wasn't understanding 'views' but have since read up on them.

Thanks again

Jon