Ken Foskey <[EMAIL PROTECTED]> writes:
> I have a requirement to distribute data efficiently and MS access
> tables are the best approach to the problem at the client end.
I strongly doubt that; I would expect that an ODBC connection to a real
SQL server, perhaps managed through MS Access, is a better solution.
> Does anyone know about replicating data with MS access,
MDB is not designed for this and, not surprisingly, it doesn't work very
well as a consequence.
> there is tools in MS access to replicate but I was wondering how this
> really works in low bandwidth situations. I was also hoping to keep
> the central server in a real database then replicate to the client
> PC's as MDB because there is already systems in place to handle the
> data and I don't want to rebuild it all.
Do you expect the clients to have read-only access to this data, or do
they have read-write access? In other words, do you also expect to
migrate data /back/ from the end user desktop?
> Finally how do you go about securing the data? I only want authorised
> people to connect and replicate.
If you are copying the entire database to the client machine then it is
absolutely, categorically, completely, under all circumstances,
impossible to secure it.
The end user can, and will, read every byte of every record at some
point. There is nothing you can do to prevent this.
Your two choices, WRT replication, are:
1. Copy only the data that the user has permission to see, and ensure
that it remains consistent even with data they cannot see.
2. Don't replicate the data, retain it under central control.
Anyway, when the only tool you have is MS Access and MDB files then your
near future looks very much like a nail. (In other words: you /will/
regret any decision that involves continuing to use MDB files.)
Regards,
Daniel
_______________________________________________
coders mailing list
[email protected]
http://lists.slug.org.au/listinfo/coders
