Code vs linked tables

[Guest]

I have a database that has been split. The front end will remain on the
users desktop while the backend will reside on the file server. I have been
informed that less bandwidth will used if I use code such as ado to connect
to the tables as oppose to creating the link within the database where you
see them in the MS access table object window.

The logic is that if the tables are linked within access without using code,
then the connection to the tables are always open until the database is
closed. With code, you can link to the table, get the records, then close
the connection without closing the database. I have not been able to find
any information on-line to help me with this debate.

My concern is time to build the database versus bandwidth issue. If someone
could point me to literature or provide advise, I would appreciate it.

CY

 

[Guest]

I dont have a definitive answer but I've been using split databases for
around 8 years and have never had to do what you suggest.
I would think that connecting, closing and reconnecting multiple times could
actually be less efficient.
Of course if you are talking about an ODBC connection to some other data
store like Oracle or a mainframe then what you suggest would make sense.

Why not code it the normal way and see if bandwidth is an issue before
trying some exotic setup?

-Dorian

 

[Guest]

Bandwidth is not an issue. Performance is.
Each time you establish a connection, you have to open the back end
database. Opening any file takes time. Linked tables are just fine.
In fact, one performance booster is the open your application with a form
that has a record source in the back end data and leave that form open as
long as your application is open. It can be hidden, but needs to stay open.
What happens in Access is that if you close all your objects that have a
table or query open, the back end database file closes, so when you open
another object that uses data from the back end, you have to wait for it to
open again.
So as long as you keep it open, you don't have to reopen it.
IMHO ADO is better suited to a true Client Server database engine. The
database engine is always running, so you don't get the file open delay.
Access is not Client Server, it is File Server. That is, with a File Server
database engine, the engine is running on the server. With Jet, it is
running on your desktop machine and has to open files on the server.

 

[Tony Toews [MVP]]

I have a database that has been split. The front end will remain on the
users desktop while the backend will reside on the file server. I have been
informed that less bandwidth will used if I use code such as ado to connect
to the tables as oppose to creating the link within the database where you
see them in the MS access table object window.

News to me. Have the informer point you to Microsoft Knowledge Base
articles or such.

The logic is that if the tables are linked within access without using code,
then the connection to the tables are always open until the database is
closed. With code, you can link to the table, get the records, then close
the connection without closing the database. I have not been able to find
any information on-line to help me with this debate.

My concern is time to build the database versus bandwidth issue. If someone
could point me to literature or provide advise, I would appreciate it.

It would take you a *LOT* longer as you'd have a lot more difficulty
using bound forms.

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/

 

[Guest]

Thank you for all the responses. You have all saved me valuable time.