Linked Server - Access

Hello there,
I have a situation where we need to transfer data from Sqlserver database to
an Access database on hourly basis.
These databases have to be on separate machines.
This access database is used across 3-4 locations as a backend for a
client-server application.
I have been able to map the access database drive on the sqlserver machine
and then made the access database a linked server. I plan to run the queries
on the sqlserver to copy data to access tables.
I was just wondering if there is a better solution available for this
problem and if there are any potential problems that we could face later on
when we go live.
Thanks for your advise.
AJHi Amit
It sounds like a MSDE backend may be more suitable than the Access backend!
Have you checked that your application will still function while the
transfer is occurring and vice-versa?
You don't say what you are copying, for example whole tables/updates etc...
If incremental changes what will happen if an update fails, can you handle
this?
Alternatives might be DTS or replication.
John
"Amit" wrote:

> Hello there,
> I have a situation where we need to transfer data from Sqlserver database
to
> an Access database on hourly basis.
> These databases have to be on separate machines.
> This access database is used across 3-4 locations as a backend for a
> client-server application.
> I have been able to map the access database drive on the sqlserver machine
> and then made the access database a linked server. I plan to run the queri
es
> on the sqlserver to copy data to access tables.
> I was just wondering if there is a better solution available for this
> problem and if there are any potential problems that we could face later o
n
> when we go live.
> Thanks for your advise.
> AJ
>
>|||Hi Amit
It sounds like a MSDE backend may be more suitable than the Access backend!
Have you checked that your application will still function while the
transfer is occurring and vice-versa?
You don't say what you are copying, for example whole tables/updates etc...
If incremental changes what will happen if an update fails, can you handle
this?
Alternatives might be DTS or replication.
John
"Amit" wrote:

> Hello there,
> I have a situation where we need to transfer data from Sqlserver database
to
> an Access database on hourly basis.
> These databases have to be on separate machines.
> This access database is used across 3-4 locations as a backend for a
> client-server application.
> I have been able to map the access database drive on the sqlserver machine
> and then made the access database a linked server. I plan to run the queri
es
> on the sqlserver to copy data to access tables.
> I was just wondering if there is a better solution available for this
> problem and if there are any potential problems that we could face later o
n
> when we go live.
> Thanks for your advise.
> AJ
>
>