Access and servers question

[Dupatt]

I am getting resistance to using Access databases at work because some
people who I believe don't know what they are talking about. I am told that
when Access runs a query from tables on a server(split database)it pulls all
of the data back to the front end then querries it, therefore using a lot of
bandwidth. If this is true, is there a way around this feature. I would
appreciate any comments on this subject. I really appreciate all you people
do to help us out here who are in the "I don't know level". TIA Pat

 

[John W. Vinson]

I am getting resistance to using Access databases at work because some
people who I believe don't know what they are talking about. I am told that
when Access runs a query from tables on a server(split database)it pulls all
of the data back to the front end then querries it, therefore using a lot of
bandwidth. If this is true, is there a way around this feature. I would
appreciate any comments on this subject. I really appreciate all you people
do to help us out here who are in the "I don't know level". TIA Pat

That is a very common assertion and it is (almost always!) WRONG.

If you have Indexes on the fields being searched, Access will retrieve only
the index (much smaller than the table), and only those records (or 2048 byte
pages) containing records which match the criteria in the query.

If you search fields that don't have indexes, or use criteria which can't use
indexes such as LIKE "*" & [Enter criteria:] & "*", or apply critera to
calculated fields then yes, it will do a full table scan. So... don't!

 

[Dupatt]

Thank you very much for your help......I should also have asked if data
entry through forms and viewing files in the form cause band width problems?
I love Access and hope to be able to convince that is is not counter
productive to run small databases on the server. Again thank you. Pat

--

I am getting resistance to using Access databases at work because some
people who I believe don't know what they are talking about. I am told
that
when Access runs a query from tables on a server(split database)it pulls
all
of the data back to the front end then querries it, therefore using a lot
of
bandwidth. If this is true, is there a way around this feature. I would
appreciate any comments on this subject. I really appreciate all you
people
do to help us out here who are in the "I don't know level". TIA Pat

That is a very common assertion and it is (almost always!) WRONG.

If you have Indexes on the fields being searched, Access will retrieve
only
the index (much smaller than the table), and only those records (or 2048
byte
pages) containing records which match the criteria in the query.

If you search fields that don't have indexes, or use criteria which can't
use
indexes such as LIKE "*" & [Enter criteria:] & "*", or apply critera to
calculated fields then yes, it will do a full table scan. So... don't!

 

[David W. Fenton]

I love Access and hope to be able to convince that is is not
counter productive to run small databases on the server.

What do you mean by "run small databases on the server"? Access
doesn't run on your server at all, in fact.

 

[Dupatt]

I guess my question was not correctly presented. Try again. I hope to be
able to convince my IT supervisor that is is not counter productive to run
small split databases with 3 or 4 tables, maybe 50,000 recordsets, backend
on the server; being accessed by 3 or 4 users with the front end on their
computer.
I hope you can make sense of that. Thanks for your reply.

 

[John W. Vinson]

I guess my question was not correctly presented. Try again. I hope to be
able to convince my IT supervisor that is is not counter productive to run
small split databases with 3 or 4 tables, maybe 50,000 recordsets, backend
on the server; being accessed by 3 or 4 users with the front end on their
computer.

One of my clients is running a database with 73 tables, 240,000 records in the
largest of them (and several tables over 100000), twelve to twenty concurrent
users. Split app of course with each user having their own frontend.

Your proposed database is VERY practical for Access. If your IT supervisor
would like to contact me directly I'll be happy to discuss.

 

[Dupatt]

Thank you very much. My IT supervisor has a control issue and he does not
like Access(probably because he knows nothing about it). He says we have
stressed bandwidth now (which is true)and MS Access would over load the
lines. He would never consult with anyone and have to admit he was wrong,
but thanks for the offer. You guys are great, keep up the good work. Pat

 

[David W. Fenton]

My IT supervisor has a control issue and he does not
like Access(probably because he knows nothing about it). He says
we have stressed bandwidth now (which is true)and MS Access would
over load the lines.

Your IT supervisor is an ignorant fool.

 

[John W. Vinson]

Your IT supervisor is an ignorant fool.

Ignorant, certainly - but in very numerous company. IT departments in general
are ignorant (sometimes willfully ignorant) of Access; and often they do have
an attitude that "all your data are belong to us" and only WE can dole it out
to you, even if you created the data in the first place.

Easy user-driven development tools like Access are a real threat to those who
would maintain tight control over all data.

 

[dddddddd]

I am getting resistance to using Access databases at work because some
people who I believe don't know what they are talking about. I am told
that
when Access runs a query from tables on a server(split database)it pulls
all
of the data back to the front end then querries it, therefore using a lot
of
bandwidth. If this is true, is there a way around this feature. I would
appreciate any comments on this subject. I really appreciate all you
people
do to help us out here who are in the "I don't know level". TIA Pat

That is a very common assertion and it is (almost always!) WRONG.

If you have Indexes on the fields being searched, Access will retrieve
only
the index (much smaller than the table), and only those records (or 2048
byte
pages) containing records which match the criteria in the query.

If you search fields that don't have indexes, or use criteria which can't
use
indexes such as LIKE "*" & [Enter criteria:] & "*", or apply critera to
calculated fields then yes, it will do a full table scan. So... don't!