472,126 Members | 1,544 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 472,126 software developers and data experts.

What effect does a network card have with Access?

If I work on my app on my standalone, things are always fast.

If I have an non-split app on the network it runs fast.

If I split the app and have both the front end and backend on the
network the app's speed drops to a crawl.

If I split the app have and make sure the MDBs use file names 8 chars
and have a persistent link to the backend it's almost as fast has having
a non-split app on the network...we're talking almost a .1 to .5 second
decrease in speed in opening, running the app.

I checked out the network card and saw the one I was using on the
network (via GoToMyPC) is a Intel with 10/100 capacity. Now I see that
there are gigabyte and 10 gig network cards. Would upgrading the cards
on the server and user PCs generate any increase in speed of loading and
running an app?

I think all of the user's PCs on the network have at least 1 gig memory.
All the PCs are relatively knew...purchase in the last couple of years
so I figure they all have good hard drives. I'm wondering about another
possible bottleneck...the network card.
Oct 14 '07 #1
2 1834
I'd say its nothing to do with your hardware...Im 99.9% sure upgrading your
network speed wont solve your problem...to be chugging down a 100mbit
betwork card means something is wrong. Having said that, I believe JET sends
all the data it needs over the network to be processed rather than on the
computer the backend resides. I doubt thats the issue tho.

I did experience a similar problem 4 or 5 years ago of which i dont recall
the solution, however my vague memory of the cure was to keep a recordset
permanently open.

I know thats not overly helpful, but I hope it leads you somewhere
John

"Salad" <oi*@vinegar.comwrote in message
news:13*************@corp.supernews.com...
If I work on my app on my standalone, things are always fast.

If I have an non-split app on the network it runs fast.

If I split the app and have both the front end and backend on the network
the app's speed drops to a crawl.

If I split the app have and make sure the MDBs use file names 8 chars and
have a persistent link to the backend it's almost as fast has having a
non-split app on the network...we're talking almost a .1 to .5 second
decrease in speed in opening, running the app.

I checked out the network card and saw the one I was using on the network
(via GoToMyPC) is a Intel with 10/100 capacity. Now I see that there are
gigabyte and 10 gig network cards. Would upgrading the cards on the
server and user PCs generate any increase in speed of loading and running
an app?

I think all of the user's PCs on the network have at least 1 gig memory.
All the PCs are relatively knew...purchase in the last couple of years so
I figure they all have good hard drives. I'm wondering about another
possible bottleneck...the network card.

Oct 15 '07 #2
John wrote:
I'd say its nothing to do with your hardware...Im 99.9% sure upgrading your
network speed wont solve your problem...to be chugging down a 100mbit
betwork card means something is wrong. Having said that, I believe JET sends
all the data it needs over the network to be processed rather than on the
computer the backend resides. I doubt thats the issue tho.

I did experience a similar problem 4 or 5 years ago of which i dont recall
the solution, however my vague memory of the cure was to keep a recordset
permanently open.
Yes. I found that you need to keep the filename 8.3. And a permanent
recordset is mandatory. Still, in my app there's a teeny-tiny miniscule
delay compared to a non-split database on the network. And there's a
difference, of course, between running the app standalone vs network.

I recognize the need to split the mdb. Everybody here says to always
split the mdb. I expect to see improvement in speed, not a degradation.
It's not something I can do. It's something MS can do.

Thanks for the input on the network card. I didn't think there'd be
much difference to warrant an upgrade of cards but better to ask and
know then wonder "what if".
>
I know thats not overly helpful, but I hope it leads you somewhere
John

"Salad" <oi*@vinegar.comwrote in message
news:13*************@corp.supernews.com...
>>If I work on my app on my standalone, things are always fast.

If I have an non-split app on the network it runs fast.

If I split the app and have both the front end and backend on the network
the app's speed drops to a crawl.

If I split the app have and make sure the MDBs use file names 8 chars and
have a persistent link to the backend it's almost as fast has having a
non-split app on the network...we're talking almost a .1 to .5 second
decrease in speed in opening, running the app.

I checked out the network card and saw the one I was using on the network
(via GoToMyPC) is a Intel with 10/100 capacity. Now I see that there are
gigabyte and 10 gig network cards. Would upgrading the cards on the
server and user PCs generate any increase in speed of loading and running
an app?

I think all of the user's PCs on the network have at least 1 gig memory.
All the PCs are relatively knew...purchase in the last couple of years so
I figure they all have good hard drives. I'm wondering about another
possible bottleneck...the network card.


Oct 15 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

121 posts views Thread by typingcat | last post: by
2 posts views Thread by Marc-André | last post: by
4 posts views Thread by Dave Kolb | last post: by
18 posts views Thread by NEWSGROUPS | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.