Retrieve Data from a Network shared drive backend database.

[PatrickH]

I maintain an Access 2003 BE db on a shared network drive that handles
between 5-10 users. I designed a local db that pulls data from the BE
db to produce daily reports. My question is: Is it better to open a
connection to the BE db through code or through a query?

 

[David W. Fenton]

m:

I maintain an Access 2003 BE db on a shared network drive that
handles between 5-10 users. I designed a local db that pulls data
from the BE db to produce daily reports. My question is: Is it
better to open a connection to the BE db through code or through a
query?

I don't understand the question.

Do you have linked tables?

Are you importing data from the shared BE to the local file, or just
using it directly in your reports?

 

[PatrickH]

I don't understand the question.

Do you have linked tables?

Are you importing data from the shared BE to the local file, or just
using it directly in your reports?

I currently import the data but have toyed with the idea of using
queries that use the BE db as the data source. I'm not using linked
tables, which is probably my first mistake. I've done some research on
this since posting here and found out that it's a good idea to use
linked tables and to open the BE db by way of DAO.

 

[David W. Fenton]

m:

[quoting me]

I don't understand the question.

Do you have linked tables?

Are you importing data from the shared BE to the local file, or
just using it directly in your reports?

I currently import the data but have toyed with the idea of using
queries that use the BE db as the data source. I'm not using
linked tables, which is probably my first mistake. I've done some
research on this since posting here and found out that it's a good
idea to use linked tables and to open the BE db by way of DAO.

The point of my questions was that if you're using linked tables,
then you don't have to use code at all.

Linked tables is the standard way in Access and you should have
extremely strong reasons to not use them. Is there some reason why
you think you shouldn't use them?

 

[a a r o n . k e m p f]

Linked tables suck dude.. for starters, adding a column requires you
do something extra to use that column.

with Access Data Projects, you can add a column and presto-chango--
you get the column automatically without refreshing all your tables
every time you open every application

[quoting me]

I don't understand the question.
Do you have linked tables?
Are you importing data from the shared BE to the local file, or
just using it directly in your reports?

I currently import the data but have toyed with the idea of using
queries that use the BE db as the data source. I'm not using
linked tables, which is probably my first mistake. I've done some
research on this since posting here and found out that it's a good
idea to use linked tables and to open the BE db by way of DAO.

The point of my questions was that if you're using linked tables,
then you don't have to use code at all.

Linked tables is the standard way in Access and you should have
extremely strong reasons to not use them. Is there some reason why
you think you shouldn't use them?