|
At 11:13 11/05/1999 , Dale Draper wrote: >IBM stumper: > >Am trying to automate the sign-on process for an Access program that calls a >user DSN to report off of AS400 data. >Client Access is set to "cache password" >Have tried both the CA connection and the DSN with a default userid. > >After signing on the 1st time and having cached the password, the user does >not see a signon box. >After rebooting the PC, the user will get the signon box, but if they escape >off it (not OK or cancel), they receive a connection. I've been puzzling over this behavior too. I've found a method that seems to work. I use a system DS. I'm not sure that it makes a difference (I'll explain). When you initially identify a DS to Access, it uses that DS as a model to create what apparently is a file DS, which it stores internally in the MDB, as part of the query or linked table definition. I have our Access designers log in using a common user ID, which has permission to read only the resources that are needed, and check the "Update on successful login" check box. Now, when Access needs AS/400 data, it connects automatically. I haven't found the location of the user ID and password. You can specify a connect string for a passthrough query, but the information is evidently kept somewhere else. Pete Hall pbhall@execpc.com http://www.execpc.com/~pbhall +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.