K
Kevin3NF
I've been putting together Access databases for 10 years. SQL Server since 1999.
So far, I've NEVER needed to use anything other than linked tables to get to my data.
That said....
I have an Access FE, Access BE, and a SQL Server that has one table I need to link to. But...the SQL Server is at a web host. I can set up a System DSN and make a connection via IP address with the correct username and password. But, when I restart the db and access that table via the form, I am prompted for the username and password again. Using a trusted connection is out, as the user's Windows account is obviously not authorized at the ISP.
So...I need some way to create that connection without the user seeing it, and have it persist the entire time the database is open.
I've read various posts in the past that made mention of loading a form when the database is opened and having it connect to a one record table in the background, but I have no earthly idea how to do that.
Is that a legitimate method, or is there something better/easier that I am just not thinking of? This needs to be simple enough to explain to my friend, and then for him to explain to his client.
All resposes welcomed and appreciated. If you feel like emailing as well as posting back to the NG, that would be cool. My email address is easily enough determined from what I posted with.
Thanks!
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
So far, I've NEVER needed to use anything other than linked tables to get to my data.
That said....
I have an Access FE, Access BE, and a SQL Server that has one table I need to link to. But...the SQL Server is at a web host. I can set up a System DSN and make a connection via IP address with the correct username and password. But, when I restart the db and access that table via the form, I am prompted for the username and password again. Using a trusted connection is out, as the user's Windows account is obviously not authorized at the ISP.
So...I need some way to create that connection without the user seeing it, and have it persist the entire time the database is open.
I've read various posts in the past that made mention of loading a form when the database is opened and having it connect to a one record table in the background, but I have no earthly idea how to do that.
Is that a legitimate method, or is there something better/easier that I am just not thinking of? This needs to be simple enough to explain to my friend, and then for him to explain to his client.
All resposes welcomed and appreciated. If you feel like emailing as well as posting back to the NG, that would be cool. My email address is easily enough determined from what I posted with.
Thanks!
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm