Re: Connection problem with Access
- From: Murray Muspratt-Rouse <Murray.Muspratt-Rouse.3d3f962@xxxxxxxxxxxxxx>
- Date: Sat, 7 Feb 2009 21:58:38 +0000
Peter, I ran debug with various 'watches' and can assure you that the
db2 code is definitely pointing at it (strCurrentFileName =
CurrentDb.Name produced the path to db2). I can also assure you that
the db1 code is pointing at db1. I think the reason that I have to
reboot follows on from trying to sign on the the database when the
pop-up tells me to do so. If I accept defeat gracefully the problem
does not occur.
When I have tried to sign in with my own user name the response is that
the workgroup file cannot be found. I am sure this happened to me
before, so I hope that powering the system down will clear whatever is
preventing the thing working.
As far as permissions go I have given myself 'administer' rights on
everything, including the database. The same goes for Admin - and I am
a member of the Admins group.
More on Monday - if anyone manages to get in to the office!
Murray
Peter Jamieson;394386 Wrote:
hello Murray,
I'm not completely sure what is going on here but...
a. if trying to access db2 is affecting db1, I wonder if you are
using
the same database pathname in both the Name and COnnection string
parameters?
b. frankly, a Word 2003 VBA reference manual is unlikely to help
because
- almost every time I have seen documentation for the
OpenDataSource method, it is wrong. That said, it is mostly "benignly"
wrong (i.e. it wouldn't matter if you followed the documentation), but
clearly written by someone who has followed earlier documentaiton and
not checked for themselves.
- /Word/ VBA reference material typically does not document the
connection strings, which are generally regarded as part of the
database
documentation.
That said, I'll try and do some tests here to check the facts. It would
be useful to know for sure which type of database security you are
dealing with - "database password" or "workgroup security file".
You may or may not know that with the workgroup security file approach,
permissions can be relatively fine-grained, e.g. an individual may have
read/write permission for tablea, read only permission for tableb, and
no permissions for tablec.
Peter Jamieson
http://tips.pjmsn.me.uk
--
Murray Muspratt-Rouse
.
- Prev by Date: Re: Incorporating PostNet Bar Code with Mail Merge
- Next by Date: Re: Formatting in attachment email merge (a la Doug Robbins)
- Previous by thread: Incorporating PostNet Bar Code with Mail Merge
- Next by thread: Re: Connection problem with Access
- Index(es):
Relevant Pages
|
