Re: Remote Database Connection with PocketPC/MSAccess Front End



thanks,
i'm going over the Compact edition books online. thers loads to understand.
when i'm done. i'll see if i have a clearer picture and then maybe get back
to you.

--
Thankfully, YisMan


"Ginny Caughey [MVP]" wrote:

Here are several things to consider. What you choose to use will depend on
your specific needs:

If you want to allow direct remote access for your Access data, I'd suggest
writing a web service which your remote apps could use.

The general problem with mobile access to remote data of any kind (including
SQL Server which Windows Mobile devices can access directly remotely) is
that sometimes the connection just isn't there. If you naturally want your
users to be able to continue to work in this situation, you have the classic
occasionally connected scenario. There are several white papers and at least
one video by Microsoft's Steve Lasker concerning this topic, but the bottom
line is that the most seamless way for your mobile app to work with
occasionally connected data is for it to always work with a local cache and
have a background worker or process refreshing that data as connection is
possible. (This is basically the Microsoft Outlook model, so everybody is
familiar with the concept.)

Generally the easiest backend data store to use for this local cache is
going to be SQL Server Compact, which supports several sync strategies
including the Access Sync Services that your question isn't about. Other
options for syncing with SQL Server include RDA and merge replication. (See
SQL Compact Books Online for details.) There is also a new product currently
in beta called Sync Services for ADO.NET which provides a more general
solution. Finally, you could roll your own syncing using web services or a
SqlClient connection to SQL Server.

--
Ginny


"YisMan" <yisman@xxxxxxx> wrote in message
news:02B6446D-5495-4831-97E0-8FE8646344DD@xxxxxxxxxxxxxxxx
Hi Everybody,

This is NOT the basic typical MS Access-PocketPC Sync question. My
question
is a bit broader so please let me know if I am not in the right group.

I develop MS Access Apps for my clients. My clients started asking me
lately
that they want to be able to connect to their database remotely,
wirelessly.
What are my options?

This specific client has his office PC where the BE is and also an
ulraportable (OQO) which he carries with him and also a pocketpc. I want
to
set him up so that he can perform CRUD operations from his devices while
he
his away.

I find that most, if not all of the PocketPC-Access sync packages that I
have researched must be synced from physical proximity. No good. Aside of
that they do not provide for the OQO.

I also checked out MS SQL server 2005 Express & Compact Edition. On the
one
hand it seems that it may be the right way to go, but I have not been able
to
figure out a few things. namely:

A. I sometimes use SQL Server Express as a backend for my Access apps, can
the same be done with CE? If yes I will be able to put the OQO's App on a
CE
backend which will be "occasionally connected" with the main BE back at
the
office.

B. Is it possible to have the regular SQL Server on the desktop and use CE
for the devices (OQO, PocketPC) only. that way I get full features on the
desktop and somewhat limited features on the device.

C. Can I have more then one device using CE out roaming, and keeping them
all in sync? cause I might in the end have multiple PPC's wanting to
collect
info for the company.

Or maybe I'm ont the wrong route alltogether and there are more fitting
tools for the problem I have

I know I might be mixing things up, cause I'm very new to this
"occasionally
conected" business.

I'd appreciate if anybody can clarify this thing for me.
Thankfully,
YisMan

.



Relevant Pages

  • Re: New to Merge/Replication
    ... although I've always used a custom sync solution since not all my customers have the infrastructure for merge replication. ... I do know of a lot of very large companies using IIS and SQL Server on the same box. ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ...
    (microsoft.public.sqlserver.ce)
  • Re: Remote Database Connection with PocketPC/MSAccess Front End
    ... If you want to allow direct remote access for your Access data, I'd suggest writing a web service which your remote apps could use. ... The general problem with mobile access to remote data of any kind (including SQL Server which Windows Mobile devices can access directly remotely) is that sometimes the connection just isn't there. ... Generally the easiest backend data store to use for this local cache is going to be SQL Server Compact, which supports several sync strategies including the Access Sync Services that your question isn't about. ...
    (microsoft.public.pocketpc.developer)
  • Re: New to Merge/Replication
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... We use sync etc. because the wireless links are not stable enough when using a mobile device to open and use a LAN connection. ... I do know of a lot of very large companies using IIS and SQL Server on the same box. ...
    (microsoft.public.sqlserver.ce)
  • Re: New to Merge/Replication
    ... We use sync etc. because the wireless links are not stable enough when using a mobile device to open and use a LAN connection. ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... I do know of a lot of very large companies using IIS and SQL Server on the same box. ...
    (microsoft.public.sqlserver.ce)
  • Re: New to Merge/Replication
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ... although I've always used a custom sync solution since not all my customers have the infrastructure for merge replication. ... I do know of a lot of very large companies using IIS and SQL Server on the same box. ...
    (microsoft.public.sqlserver.ce)