[AccessD] Connection strings and Access security

Never mind, it was a Security issue  --  you have to allow the "Users" group to have Database permissions of 'Open Exclusive'.  I had removed this as part of the conversion to the new MDW. 

I really should have known that (lol) ...

Stephen Bond


-----Original Message-----
From: Stephen Bond 
Sent: Friday, 7 March 2003 11:56 a.m.
To: accessd at databaseadvisors.com
Subject: [AccessD] Connection strings and Access security


I am trying to establish a DAO connection to do a Word mailmerge.  It has been working fine up till I changed the MDW to force users to log in to the MDB front end.  Below is the code that has worked up till the change.

After the change, this statement proceeds to open another version of Access using the default MDW (user=admin), and the app traps this eventuality in the AutoExec code and closes down that instance of Access forthwith.

I have looked at the OpenDataSource method in M$ Help, and have tried certain combinations to no avail, I suspect the keywords UID and PWD could be the key to this ...

Any suggestions?  BTW Access 2000, Word 2000.

</snip>
  With objWord.MailMerge
    .MainDocumentType = wdFormLetters
    .OpenDataSource _
        Name:=GetDBDir() & "\" & "ComplianceSchedulePROG.mdb", _
        LinkToSource:=True, _
        Connection:="QUERY qryComplianceRenewalCandidates"
       .Execute
  End With
</end snip>



TIA

Stephen Bond 
Otatara, New Zealand
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com