Opinions: client, embedded offline database and synchrony with backend

Hello folks,

First, excuse my ignorance. I am writing to inquire if the idea I have
in mind is possible, then I will jump into the solution or find/hire someone
to do it for me.

Here's the goal:

I want to design a platform-independent client front-end that has its own
database (embedded or otherwise) with the capability to synchronize records
with a client-owned table in a backend. In other words, each client has a
table in the backend and their front-end app should permit synchronization
with their backend table with the click of a button. I only want one
solution for all clients, i.e. depending on initial set-up of
username/password in the client's front-end, this will dictate the table in
the backend for which they can append or update records. I don't want to
have to design a slew of solutions for all clients but a one-size-fits-all.
The front-end should also have the ability to locally import and export text
files into their local database. The front-end must also have the equivalent
of Access' pass-through queries whereby clients can run pre-configured
queries to the backend. Of course, the client must not be able to view or
manipulate any of the connection strings to the backend so the solution must
be compiled. Finally, if and when I make changes to the client front-end, I
would like to be able to have clients download and install a new front-end
without doing anything to the contents of their local database.

I merely want to know if the above is possible, but if anyone can offer a
place to start with such a solution, I would be greatly appreciative. I have
an Access *.mde solution that does exactly the above and works great, but I
am desperate to get a platform-independent solution and making updates to
the front-end is a pain in the neck because it means I have to force the
client to jump through hoops.

Dave

--
______________________________
Remove "_SPAM" to reply directly.


.

Quantcast