Server Side Vs Client Side Queries

[wricoasolutions]

I have split my database, the data is in a DB on the server and the forms, reports, etc is on the client desktop. My question is "Is there an advantage to having all of my combo box queries (Lookups) on the server side (defined in the table as a combo lookup) or should I put the all on the form so that they reside in client side DB.

 

[KenHigg]

I would put them all on the client, simply for house keeping reasons like having to wonder/worry where one might be...

 

[wricoasolutions]

Thanks Ken, Kind of was leaning that way myself, but am new to Access and did not know how it handled the different coding methods.

Again, thanks for the reply.

Bill

 

[Pat Hartman]

Even though the queries are stored as querydefs in the Access .mdb, most of the time Jet will pass them through directly to the server even though they are not defined as pass through queries. Do read the kb articles on client/server optimization to see what things cause Jet to bring the data to the client so the query runs locally rather than sending the query to the server to run there.

 

[KenHigg]

Something tells me he's talking of a straight file server set up here... ?

 

[wricoasolutions]

Clarification!

I Have in the past worked in an Oracle environment and have had code that is left on the server for various reasons. I was/am not sure how or if Access can handle server side coding. From what I am reading and hearing it would appear that it does not. It also appears that Access is similar to FoxPro in that when a table is accessed for a query the entire file is passed to the application for handling. Knowing that I can develop my application with these limits in mind.

Pat: You mentioned a document that I should read on client/server processing, is this specific to Access or is it related to general functionality. Not knowing my way around the forum and/or where documents of this nature are located could you point me in the direction of the document in question. Much appricated........

Thanks for the information and all the help. Will give me the insite to finish the app I am working on.

Bill

 

[Pat Hartman]

It is not clear to us whether your back end database is Jet or something else. Jet is a FILE server. It is not a database server and therefore does not have a server side process that runs waiting for queries.

An Access front end linked to an Oracle, DB2, SQL Server, etc. back end works effectively because Jet is smart enough to send "most" queries directly to the back end server for processing. To understand "most", you need to search the MSDN library and kb for articles on client/server optimization.

 

[wricoasolutions]

It a Jet backend.

Sorry, it's a Jet backend. Have been searching the forum and have found that the Jet backend will not do what I thought it would, (process server side code). By the way there were some good responses from you Pat in my searches. Thanks for the info.. Problem I have is that I can only use Native Access, do not have the choice of MySequel or any of the other DB Server software. So I will have to make the best of what I have and make it run as fast and error free and is possible to do.

Again, Thanks for the info and help.

Bill