J
Joe
I have experienced security issues whilst attempting to
read data on a remote database using DAO. I posted a
question regarding this problem on the Community Newsgroup
forms programming site. I have received lengthy advice
from a patient mentor, but unfortunately have not been
able to overcome the problem. The final advice I have
reproduced below. I would like to attempt the suggested de-
securing of the two databases, but have been unable to
find information on this process. If anyone knows how to
approach this issue or where I can obtain information I
would be grateful. I have full rights to both tables and
all passwords.
Final reply from forms programming user group:
1) You used the existing system default workgroup file,
when you secured
the database. That would be an error. You start the
securing process by
creating a *new* workgroup file, not using the existing
system default one.
Or:
(2) You *did* create a new workgroup file, but you have
missed one or more
steps in the process - because, your "secured" database
can be referenced
from the *default* workgroup file.
Or:
(3) You did create a new workgroup file, & you have now
set that file as the
default workgroup file, using the workgroup administrator
program (or option
in later versions of Access). That would not be
an "error", as such, but it
would cause problems with all your other databases, so
most people would not
go that way.
Joe, I hate to give up on this problem after all the work
that we have done
so far! But the above conclusion suggested that you have
not set up the
security properly.
These kinds of problems are really, really difficult to
diagnose remotely.
At this stage, here is all I can think to suggest.
(1) Get someone local to come over & take a look at it. Or,
(2) *Desecure* both databases, then start again, using a
formal reference
such as the Access Security FAQ, following the steps
precisely, adding &
omitting nothing.
Finally, if you want to open a second database (from the
current one) but
using a different workgroup file, check out the
PrivDBEngine object. You'll
find some references to it on the web. The code is
something like this
(untested):
dim dbe as PrivDBEngine, db as Database
set dbe = new privdbengine
dbe.systemdb = "path to other workgroup file"
dbe.user = "fred"
dbe.password = "s3cr3t"
set db = dbe.opendatabase( ...)
etc.
Sorry to leave you in limbo, but I really can't do much
more by remote control.
read data on a remote database using DAO. I posted a
question regarding this problem on the Community Newsgroup
forms programming site. I have received lengthy advice
from a patient mentor, but unfortunately have not been
able to overcome the problem. The final advice I have
reproduced below. I would like to attempt the suggested de-
securing of the two databases, but have been unable to
find information on this process. If anyone knows how to
approach this issue or where I can obtain information I
would be grateful. I have full rights to both tables and
all passwords.
Final reply from forms programming user group:
1) You used the existing system default workgroup file,
when you secured
the database. That would be an error. You start the
securing process by
creating a *new* workgroup file, not using the existing
system default one.
Or:
(2) You *did* create a new workgroup file, but you have
missed one or more
steps in the process - because, your "secured" database
can be referenced
from the *default* workgroup file.
Or:
(3) You did create a new workgroup file, & you have now
set that file as the
default workgroup file, using the workgroup administrator
program (or option
in later versions of Access). That would not be
an "error", as such, but it
would cause problems with all your other databases, so
most people would not
go that way.
Joe, I hate to give up on this problem after all the work
that we have done
so far! But the above conclusion suggested that you have
not set up the
security properly.
These kinds of problems are really, really difficult to
diagnose remotely.
At this stage, here is all I can think to suggest.
(1) Get someone local to come over & take a look at it. Or,
(2) *Desecure* both databases, then start again, using a
formal reference
such as the Access Security FAQ, following the steps
precisely, adding &
omitting nothing.
Finally, if you want to open a second database (from the
current one) but
using a different workgroup file, check out the
PrivDBEngine object. You'll
find some references to it on the web. The code is
something like this
(untested):
dim dbe as PrivDBEngine, db as Database
set dbe = new privdbengine
dbe.systemdb = "path to other workgroup file"
dbe.user = "fred"
dbe.password = "s3cr3t"
set db = dbe.opendatabase( ...)
etc.
Sorry to leave you in limbo, but I really can't do much
more by remote control.