InstantForum.NET v4.1.4StrataFrame Forumhttp://forum.strataframe.net/forum@strataframe.netFri, 21 Nov 2008 15:29:40 GMT20http://forum.strataframe.net/Topic12908-21-1.aspxNo problem...</P><P>The only other option would be to set the connection string programmatically and store it somewhere else.Thu, 06 Dec 2007 09:36:49 GMTBen Chasehttp://forum.strataframe.net/Topic12908-21-1.aspxThanks Ben! I thought of the connections.dat and appkeys.dat deployment option but wanted to verify there were not better approaches. Thanks!Thu, 06 Dec 2007 09:20:28 GMTDouglas Rileyhttp://forum.strataframe.net/Topic12908-21-1.aspxNo, you cannot place the shared settings file on a web resource. If your users do not have access to the same network resource, then you could just deploy the Connections.dat and the AppKeys.dat files to the All Users\MicroFour\ConnectionData folder.</P><P>Also, if you don't want the users to enter the connection data at all, then don't use the ConnectionManager class. Just store the connection string anywhere... even in an app.config file and set it programmatically rather than using the ConnectionManager class.Thu, 06 Dec 2007 09:13:53 GMTBen Chasehttp://forum.strataframe.net/Topic12908-21-1.aspxIs it possible to have winform users access a shared settings file located on a web server (example: via <A href="http://www.sitename.com/">http://www.sitename.com</A>) instead of an internal network drive?<P>If not, is it best to include a shared settings file during deployment to each user and send out settings file updates when necessary? I am trying to avoid having to give users database account info (username, password) during initial win app setup :unsure:. </P><P>Thanks!</P><P>DougThu, 06 Dec 2007 07:37:30 GMTDouglas Riley