Frank Tanner III
pctech at mybellybutton.com
Tue Aug 26 07:23:37 CDT 2003
Strictly from a security standpoint I would NOT put a SQL server out on the "big bad Internet" without some sort of protection. If it were me, I'd put it behind a firewall, a REAL firewall, not that crap that comes with Windows XP, and then have the client workstations VPN into the firewall and connect to it via ODBC. You do not want all of that unencrypted data flowing across the Internet, nor do you want to leave that SQL server exposed. --- "Stephen R. Zayko" <szayko at secor.com> wrote: > Dear group: > > I was wondering if I could get some input for the > following scenario: > > I am writing an AccessXP FE for a MS_SQL Server > database that will live > on the internet. I was wondering how would be the > best way to connect > to the data (only I can TRULY answer this question)? > But in asking > myself that, I was wondering what the pros and cons > of each of these are > and if anyone has strong feelings one way or another > on these: > > 1) Linked tables via ODBC (using system DSN) > 2) Write the FE as an .adp with tables directly > connected to server > tables > 3) Call all connections on the fly to the server > where the BE is > located > 4) Some other way that I do not know about. > > Most users will have an DSL or T1 connection to the > internet. > > Thanks in advance for your inputs. > > -Stephen Zayko > > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com