DB Comparison
PosseJohn
Without the ability to place on an internet server (A2010), I need the
ability for each user to use the DB, and then send the DB to the other
users. Once received, I need a way of incorporating the changes that the
first user made into the recipients copy of the DB.
How do I structure the DB so that I can detect which records were
edited/changed and transfer them into the other users DB?
If both users happen to edit the same record and then one of the users
receives the other users copy, is there a way to ascertain which field might
have changed and which would be more up to date?
Any suggestions would be greatly appreciated.
Banana
Though you may be using 2007, you still can use replication if you're
using .mdb format rather than .accdb. That's one possible option. If I'm
not mistaken, to work across WAN, indirect sync will be necessary which
complicate the setup as well.
The other option is to set up a terminal server so all users can log in
remotely and thus use the same database (mind, everyone must have their
own copy of front-end linking to a common backend). This is still doable
even on a .accdb format.
Yet another option is to move the data into a server-based RDBMS. Note
there are free RDBMS such as SQL Server Express, MySQL, Firebird,
PostgreSQL and some more. The Access application still can be used and
can be link to those table across the internet without concern for
corruption. Do note, though, you need to consider the security (e.g. use
a VPN or similar encrypted connection) when working across WAN.
It is my belief that those options, especially #2 and #3, is far more
simpler & robust than any kind of DIY replication we could roll out.
PosseJohn
When you mention a terminal server, would that basically be a computer that
is connected to the internet, and users gain access remotely to that
computer? What program/how do they gain access remotely?
Where would I be able to learn about setting that up with security in mind?
"Banana" <Banana@Republic> wrote in message news:4B58CCC0.20209@Republic...
Banana
> Forgive my ignorance...
>
> When you mention a terminal server, would that basically be a computer
> that is connected to the internet, and users gain access remotely to
> that computer? What program/how do they gain access remotely?
>
> Where would I be able to learn about setting that up with security in mind?
Basically, yes. Note, however, "Terminal Server" is a name of software
owned by Microsoft. There are other softwares that does similar things,
Citrix at high end and Crossover at low end.
What they gain access to depend on the software and how you configure.
For example, Citrix provide you with a window into a specific
application (you can't see the desktop at all) while Terminal Server
uses "Remote Desktop Connection" to log you into a remote desktop which
you can use just like any other computer. In such cases, you would want
to set up this desktop to contain only applications users should be able
to use and restrict their privileges.
The question would depend a lot on what is your spending budget and what
you really need, then deciding on what software would best fit your
needs. Keep in the mind that often, those also need Client Access
Licenses which restrict the numbers of users that can log in, as well
whether they would be licensed to use those applications on the remote
desktop, so take those into consideration as well.
Wiki has a nice list of different softwares...
http://en.wikipedia.org/wiki/Comparison_of_remote_desktop_software
HTH.
Dominick DeLeone
On 1/21/10 5:22 PM, in article 4B58D39A.60203@Republic, "Banana"
GBA
internet and not a high speed private WAN with Terminal Services capabilities…
Option 1 – stay with Access’ embedded replication feature (if .mdb format –
not available with .accdb 2007 format) presuming you can co-locate or vpn
them together.
Option B is to go with web architecture. find a web developer - turn over to
him/her your Access db for them to look at as the prototype design...and get
their quote. You will pay to have them develop it and then there will be the
recurring for the hosting company...
Option III is the www.AccessTables.com service; this allows everyone to
operate a copy of the Access db locally and then you send in the tables -
they consolidate/replicate all the data - - and return to everyone a
consolidated set of tables. Is great as long as the requirement is not for
instantaneous shared data. If periodic updates is sufficient and the user
base are all part of a team - this can be a good solution.
Option 3.5 is an online commercial db service - I would recommend
DabbleDB.com Intuit also has a product : QuickBase - but it is quite
pricey and intended for corporate users. Dabble is very reasonably priced
and pretty cool. When using a db service you are in their sandbox and must
live with the features and look they offer; the redesign using Dabble is a
bit of work & learning and there is definitely missing many features one
takes for granted in Access.
Option 5 is to have users get into Access using a commercial VPN service
such as www.GoToMyPC.com. This will also have a monthly fee. The PC must
always be on for the user. A bit of a latency/lag experience. Only one user
can log on at a time...and, importantly, the log on user will have the
ability to see everything on the PC - not just the Access application....
Option VI assuming you have Access07 or later in .accdb format you can get a
sharepoint hub and use the publish/off-network function as a mode to work
locally but push the data back & forth to a sharepoint hub. But sharepoint
itself is another big element to manage and you might look to a shared
sharepoint service from Microsoft or others.
No right or wrong per se – just right or wrong for one’s situation…finding
the right tool for the job…or redefining the job for the available tool…..
ITISAdmin
"PosseJohn" <poss...@yahoo.com> wrote in message
news:F10A580B-43B1-44F3...@microsoft.com...