Where to set registry, Client or Server ?

  • Thread starter Thread starter Albert
  • Start date Start date
A

Albert

Hello Expert,

I use AccessXP with DAO + ADO to JET database. Database is split. On file
server, database contains tables. On client, database contains linked table
and other Access objects.

If I want to change the registry setting for JET, Where (client or server)
that I have to set ?

Thank you
Albert
 
This will have to be done on the client. When a user launches the client
app, or any app for that matter, it will read the local (client) registry.
An Access database on a file server is a passive file. All processes are
executed on the client machine.
 
Excuse me, May I ask you more.

I ever posted to newsgroup about What is the type of cursor generated from
ADO if my connection string is point to .mdb location on server? Someone
replied that it is server-side query. It is executed on server. Is that
correct ? If yes, registry should be changed on server ?

Thanks again
Albert
 
Albert said:
Excuse me, May I ask you more.

I ever posted to newsgroup about What is the type of cursor generated from
ADO if my connection string is point to .mdb location on server? Someone
replied that it is server-side query. It is executed on server. Is that
correct ? If yes, registry should be changed on server ?
Click to expand...

A file is a file is a file is a file.

A horse is a horse is a horse.

When using JET as a file share, you are opening a file on the server. This
is no different from opening a word file on the server, opening a Excel file
on the server, and also opening a mdb file on the server.

There is no processing, or nothing at all happening on the server side. You
do not have to install JET on the sever, In fact, you don't install ANY
SOFTWARE on the server in regards to using JET. So, if you don't install
anything on the server, then how could possibly any settings, or any type of
cursor exist on the server?

Simply put, you have a dumb file on the server, and you are opening it like
any other windows file. You can move that file to your local computer, or
even move the file to a shared folder on the computer sitting next to your
computer. A file is a file is a file.

You do DOING NOTHING MORE THEN OPENING a simple windows file. The fact that
you can place the database on a computer that does not even have
JET/ms-access installed, and open it should make this clear.

Again, you are simply opening a file. You can open a Excel file, You can
open a Word file, you can open a mdb file. All of the above opening of files
is exactly the same.

Remember, you are using a file share, and that computer that has the file
on it does not care or even know that the file is a word file, a excel file,
or ms-access file. You are just opening a plan old file. The server has no
idea that his file is ms-access, and nor does it care.

I mean, when you open a word file on the server, does the server need word
installed? You are dealing with a simple file share, and thus all
processing, code etc. is running on YOUR computer. This whole affair is not
different from opening a word file. You don't need to install word on the
server when you load a word file from that dir on the server. The same
applies to ms-access, you JUST OPENING a file. No special processing, or
anything else occurs on the server when you open a word file from that
server. With ms-access, once again, nothing occurs on the server, except
some windows file open.
 
replied that it is server-side query. It is executed on server.

No it is not.
It is a client side query, and it is executed on the client.

ADO always starts a client side database engine to deal with
..mdb files, even if the file is somewhere far away. The
client side database engine is controlled by registry settings
on the client.

You may make registry changes on the File Server for the File
Server. For example, you may wish to change file caching or
file locking behaviour to make your File Server run faster or
better.

(david)
 
Back
Top