[AccessD] Replicated .mdb and SQL Server

Here is a starting point on SQL Server Replication,
http://www.informit.com/articles/article.asp?p=169612&seqNum=3
You are going to have to decide whether you can get by with Merge 
replication and MSDE
or buy multiple SQL licenses to handle full transactional replication. I 
am not sure if SQL 2005 Express
(the latest Beta incarnation of MSDE) handles transactional replication.
You will have to look at the requirements for the salesman, do they need 
access to real time data
and or will they have almost constant internet connections via wireless 
like a blackberry or cell phone connections.
with this you might get away with running multiple Access FE's to a 
single remote SQL server. Connection coverage areas
than enter the picture, if you have salesmen going out to places like 
Moose Pasture Saskatchewan, this may present problems.
So you may want a pushed merged copy of  the latest data on a MSDE to 
use when no connection is present.
Then there maybe a question of using VPN for connection security.
There is a whole series of articles on SQL replication here.
http://www.databasejournal.com/features/mssql/
search on sql replication
 You realize that even some experienced SQL DBA's feel unsure of 
themselves getting into replication.
So you may want to go with the simple Access FE to a remote SQL Server.
Barbara Ryan wrote:

>Regarding "Do you plan on running replicated SQL server or updating via the
>internet and SQL Server?"
>
>---- I don't know!  I know very little about SQL Server.  I am open to any
>suggestions on how I can handle this situation (i.e.,  the Access
>application (front end) is linked to 2 separate back end .mdbs.  Backend "A"
>contains the majority of the data tables for the application; Backend "B" is
>a replicable database that is also used as the sole backend database for
>another Access application that is used by salesmen on their laptops.   The
>front end contains some queries that currently join tables from both Backend
>"A" AND Backend "B".)
>
>Could the salesmen use an Access backend and somehow synchronize it with a
>SQL Server database?
>
>Thanks,
>Barb Ryan
>
>
>
>----- Original Message ----- 
>From: "MartyConnelly" <martyconnelly at shaw.ca>
>To: "Access Developers discussion and problem solving"
><accessd at databaseadvisors.com>
>Sent: Wednesday, March 30, 2005 5:10 PM
>Subject: Re: [AccessD] Replicated .mdb and SQL Server
>
>
>  
>
>>I don't know if the Access to SQL upgrade wizard handles replicated
>>databases but here is an unreplicator just in case
>>http://www.trigeminal.com/lang/1033/utility.asp?ItemID=7#7
>>Do you plan on running replicated SQL server or updating via the
>>internet and SQL Server?
>>
>>Barbara Ryan wrote:
>>
>>    
>>
>>>I currently have an Access application, split into a front end linked to
>>>      
>>>
>2 separate back end .mdbs.  Backend "A" contains the majority of the data
>tables for the application; Backend "B" is a replicable database that is
>also used as the backend database for another Access application that is
>used by salesmen on their laptops.
>  
>
>>>The client is considering migrating the data for this application to SQL
>>>      
>>>
>Server.  Any ideas on how to handle this?  The front end contains some
>queries that currently join tables from both Backend "A" AND Backend "B".
>  
>
>>>Thanks,
>>>Barb Ryan
>>>
>>>
>>>      
>>>
>>-- 
>>Marty Connelly
>>Victoria, B.C.
>>Canada
>>
>>
>>
>>-- 
>>AccessD mailing list
>>AccessD at databaseadvisors.com
>>http://databaseadvisors.com/mailman/listinfo/accessd
>>Website: http://www.databaseadvisors.com
>>    
>>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada