MS SQL Server - Replicate SQL Server to MS Access MDB

Author

Replicate SQL Server to MS Access MDB

shane1812

2006-10-24, 6:29 pm

From: shane1812 - view profile
Date: Tues, Sep 19 2006 3:03 pm
Email: "shane1812" <s...@moorhousefarm.co.uk>
Groups: comp.databases.ms-sqlserver
Not yet ratedRating:
show options
Reply | Reply to Author | Forward | Print | Individual Message | Show
original | Remove | Report Abuse | Find messages by this author

Hi,

I need to create an app where all the data is store on an SQL db on the

server but allow users to take their laptops off-line (eg: if visiting
client) and so would like to be able to set up replication to an MDB on

each laptop.

I've looked in to merge replication. It seems to take some configuring
and my app needs to be installable by dummies!! A server install then
workstation setups.

Any sugestions?

As a last resort I could write a .net module to manage replication but
surely there's a better way!

Thanks

Uri Dimant

2006-10-24, 6:29 pm

Hi
Do the users have the .MDB file on his/her laptops while they are visiting
clients?

Have you considered using linked servers or OpenDataSource command?

"shane1812" <shane@moorhousefarm.co.uk> wrote in message
news:1158674817.713466.64430@d34g2000cwd.googlegroups.com...
> From: shane1812 - view profile
> Date: Tues, Sep 19 2006 3:03 pm
> Email: "shane1812" <s...@moorhousefarm.co.uk>
> Groups: comp.databases.ms-sqlserver
> Not yet ratedRating:
> show options
> Reply | Reply to Author | Forward | Print | Individual Message | Show
> original | Remove | Report Abuse | Find messages by this author
>
>
> Hi,
>
> I need to create an app where all the data is store on an SQL db on the
>
> server but allow users to take their laptops off-line (eg: if visiting
> client) and so would like to be able to set up replication to an MDB on
>
> each laptop.
>
>
> I've looked in to merge replication. It seems to take some configuring
> and my app needs to be installable by dummies!! A server install then
> workstation setups.
>
>
> Any sugestions?
>
>
> As a last resort I could write a .net module to manage replication but
> surely there's a better way!
>
>
> Thanks
>

shane1812

2006-10-24, 6:29 pm

Hi, The users will have the .MDB on their laptops.

The plan is, is that when connected to the network the app will
communicate directly with the SQL server. there will be a 'sync on
exit' option so that when they are about to disconnect from the network
they can update their .MDB file.

If they work on their app away from the office and modify the data,
upon return to the network replication needs to take place.

Hope that made sense!

I'll investigate the two options you suggested.

Thanks

Steen Persson (DK)

2006-10-24, 6:29 pm

shane1812 wrote:
> Hi, The users will have the .MDB on their laptops.
>
> The plan is, is that when connected to the network the app will
> communicate directly with the SQL server. there will be a 'sync on
> exit' option so that when they are about to disconnect from the network
> they can update their .MDB file.
>
> If they work on their app away from the office and modify the data,
> upon return to the network replication needs to take place.
>
> Hope that made sense!
>
> I'll investigate the two options you suggested.
>
> Thanks
>
>
Hi

What you are trying to achieve, is not as simple as is sounds...:-).
There are a lot of eventualities that you have to think about.
E.g. what happens if the user make some changes to an existing record
while he is on the road and then somebody else make other changes to the
same record in the office? Which of those changes are going to win?
Should it be the newest? Should the user(s) be asked which one to keep
when it happens?
Also, what about deletions? What happens if a user make changes to a
record while he is on the road, and then somebody else delete the record
in the office. When he synchronise then the record will be deleted or....?
You should also make sure that you know what happens if the user
un-docks his computer while it's still synchronising? Most users tend to
be impatient and can't way until their computer is shut down properly
before they are un-docking it an leaves the office.

--
Regards
Steen Schlüter Persson
Databaseadministrato
r / Systemadministrator

shane1812

2006-10-24, 6:30 pm

Thanks for highlighting those scenarios. I think, given that there
doesn't really seem to be anything out their that will work in the
manner I'd like it to I'll write the module myself and be sure to
accomodate these scenarios.

Thanks for the input.
[color=darkred]
> Hi
>
> What you are trying to achieve, is not as simple as is sounds...:-).
> There are a lot of eventualities that you have to think about.
> E.g. what happens if the user make some changes to an existing record
> while he is on the road and then somebody else make other changes to the
> same record in the office? Which of those changes are going to win?
> Should it be the newest? Should the user(s) be asked which one to keep
> when it happens?
> Also, what about deletions? What happens if a user make changes to a
> record while he is on the road, and then somebody else delete the record
> in the office. When he synchronise then the record will be deleted or....?
> You should also make sure that you know what happens if the user
> un-docks his computer while it's still synchronising? Most users tend to
> be impatient and can't way until their computer is shut down properly
> before they are un-docking it an leaves the office.
>
>
> --
> Regards
> Steen Schl=FCter Persson
> Databaseadministrato
r / Systemadministrator[
/color]

Sponsored Links