Speeding Up App Across LAN?

[Tony Toews [MVP]]

I just can't figure out what the KB article means by "number of
connections". Concurrent open recordsets?

That's never made a lot of sense to me either.

Thanks for reminding me to ask MS about this.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

Maybe this makes me a closet Type-A, but I find anything over
sub-second response time tb irritating - and I'm assuming that
most of my users are similarly affected.

I've found most users are of the ummm, ahhh, ohhhhh type. <smile>
Although there are a few that are impatient as am I.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[(PeteCresswell)]

Per David W. Fenton:

If wireless is required, you just can't use a
Jet back end, period, end of statement.

In another thread, it's looking like a terminal server might be a
workaround for that limitation.

 

[(PeteCresswell)]

Per Tony Toews [MVP]:

I've found most users are of the ummm, ahhh, ohhhhh type. <smile>
Although there are a few that are impatient as am I.

The ones that drive me up the wall are those that go on and on
about how wonderful my application is.

I think "Geeze guys.... this thing was written by one person
working his brains out all day every day to a totally unrealistic
deadline in traditional IT terms. You think it's so wonderful?
Guess what? It's *full* of bugs and there's probably at least a
dozen things you want but didn't think to ask for and which I
failed to second guess for you."

Call me a masochist, but I'll take the
in-your-face-never-really-happy user every time. If nothing
else, at least I can relate to them.

 

[David W. Fenton]

Per David W. Fenton:

In another thread, it's looking like a terminal server might be a
workaround for that limitation.

Yes. I highly recommend Terminal Server. I wouldn't recommend it so
much for performance problems, though, as I think it's better to
optimize the app to try to engineer out the performance bottlenecks.

 

[(PeteCresswell)]

Per David W. Fenton:

Yes. I highly recommend Terminal Server. I wouldn't recommend it so
much for performance problems, though, as I think it's better to
optimize the app to try to engineer out the performance bottlenecks.

I was thinking in terms of an app that's running pretty much as
fast as can be expected over a LAN connection to the back end.

Right away, I see a 25-30% reduction in response time just by
going to a terminal server with the same performance as my
desktop PC.

The prospect of remoting to a super-box and getting even faster
response for my users running concurrently than I get on my
developer box running solo practically has me salivating.

I think I'm going to schmooze with the client's LAN guys and see
if I can wheedle a loaner box from them to play around with for a
few weeks.

No cost to the client.... maybe put a demo icon on a few desktops
and let them decide if they want to go the extra bucks.

Besides, I get to play around a little.... -)