Re: Split DB over the internet with SQL backend?

"(PeteCresswell)" <x@xxxxxxxxx> wrote in
news:s6vm429dm5qt91g62o7h45m98iob3aeks3@xxxxxxx:

If you are using local work tables and are not adhering to the MS
standard that says those tables should be under C:\Documents and
Settings\[UserName], you will have to rewrite whatever code you
use to create work tables and also do some kind of workaround for
MakeTable queries that write to a temp DB.

Another note on this:

The MS standard has nothing to do with "those tables" and where they
should be stored. It's simply a result of locking down the system to
prevent modification of system and application files by
non-administrative user processes.

Under the default locked-down scenario (in place since Win2K, i.e.,
since 1999!), any user data that has to be writable (which includes
an Access front end MDB) must be stored under the user's profile,
which is globally writable to user-level logons (which is what
should be in use, rather than admin-level logons).

Another advantage of this is that in a domain where roaming profiles
are in use, the user's same front-end MDB will be available at any
workstation they sit down at. If you're storing user settings in
that front end (either in tables or database properties), those will
follow a user with roaming profiles *if* the front end is stored in
a folder under the user's pofile folder.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.