I am migrating an Access 97 (Jet) Application to Access 2000 (MSDE) and
wondering if there's a way to connect a Project to more than one database.  It
seems that File / Connection only permits 1 database's tables to show in the
Database Window, and only those objects may be used to build Views, etc.  My
application requires Server data but also includes Views and Forms based on a
local database when running on a Client - do I have to set my connection to the
Server database and then use ADO for the local one?  In Access 97 I used a
front/back approach with links pointing to different machines. Thanks very much,
I'm new to Access 2000 and have spent days trying to find this.

Wayne Miller

Wayne

You can only have one active connection at a time - so you can only
connect to a single database. What sort of data will be held in the
local database? Can it be stored elsewhere?

Brian

-----Original Message-----
From: Wayne Miller [mailto:talex@s...] 
Sent: 22 January 2003 19:11
To: Access
Subject: [access] More Than One Database
Importance: High

I am migrating an Access 97 (Jet) Application to Access 2000 (MSDE) and
wondering if there's a way to connect a Project to more than one
database.  It
seems that File / Connection only permits 1 database's tables to show in
the
Database Window, and only those objects may be used to build Views, etc.
My
application requires Server data but also includes Views and Forms based
on a
local database when running on a Client - do I have to set my connection
to the
Server database and then use ADO for the local one?  In Access 97 I used
a
front/back approach with links pointing to different machines. Thanks
very much,
I'm new to Access 2000 and have spent days trying to find this.

Wayne Miller

Hey Brian,

Thanks for the answer.  My application is a point of sale, with client "selling
stations" and a central Server with customer and product master files, etc.
Prior to entry the client takes a copy of this data to it's own "local"
database.  Thus order entry is fast as it requires no network traffic.  The
completed orders are sent to the server by a background process.

I believe I can open several databases at a time with ADO connections, but then
I don't see tables in the database window that I can use to create views, etc.
I am thinking there would be a service running on the server in this case (my
main connection), but then there are forms in the client application that rely
on tables on the client itself (another service running here?).

Does this help?  If you have any input here it sure would be appreciated.

Thanks, Wayne

Brian Skelton wrote:

> Wayne
>
> You can only have one active connection at a time - so you can only
> connect to a single database. What sort of data will be held in the
> local database? Can it be stored elsewhere?
>
> Brian
>
> -----Original Message-----
> From: Wayne Miller [mailto:talex@s...]
> Sent: 22 January 2003 19:11
> To: Access
> Subject: [access] More Than One Database
> Importance: High
>
> I am migrating an Access 97 (Jet) Application to Access 2000 (MSDE) and
> wondering if there's a way to connect a Project to more than one
> database.  It
> seems that File / Connection only permits 1 database's tables to show in
> the
> Database Window, and only those objects may be used to build Views, etc.
> My
> application requires Server data but also includes Views and Forms based
> on a
> local database when running on a Client - do I have to set my connection
> to the
> Server database and then use ADO for the local one?  In Access 97 I used
> a
> front/back approach with links pointing to different machines. Thanks
> very much,
> I'm new to Access 2000 and have spent days trying to find this.
>
> Wayne Miller
>
>

Wayne

If you're willing to go with unbound forms and controls, then you can 
create and destroy connections from code as needed.

On the other hand, this looks like a classic replication scenario to me, 
with a central main datastore and a number of remote replica databases. 
From the small amout of reading I've done on SQL Server replication the 
central database would do all the work keeping the databases synchronised -
 pushing and pulling data around on a regular basis.

Any help?

Brian

> Hey Brian,

Thanks for the answer.  My application is a point of sale, with 
client "selling
stations" and a central Server with customer and product master files, etc.
Prior to entry the client takes a copy of this data to it's own "local"
database.  Thus order entry is fast as it requires no network traffic.  The
completed orders are sent to the server by a background process.

I believe I can open several databases at a time with ADO connections, but 
then
I don't see tables in the database window that I can use to create views, 
etc.
I am thinking there would be a service running on the server in this case 
(my
main connection), but then there are forms in the client application that 
rely
on tables on the client itself (another service running here?).

Does this help?  If you have any input here it sure would be appreciated.

Thanks, Wayne