I'm just embarking on a major project that will be using VP for the front end and SQL as the database backend. I'm looking for opinions/experiences of this with regard to logging in to the database. Did you use the old VFP way of a user table and checking passwords there, whilst using a single SQLlogin for the app to access the database? Or did you soley rely on SQL logins? Or a combination of both so you have an audit trail of unqie SQL logins, plus an application table defining users permissions to tables/screens etc?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SQL Security with VFP front end.
- Thread starter finsys
- Start date
Hi,
You could have SQL use windows NT/2000 security. Anyone that is not setup in the domain with a username/password would not be able to gain access to SQL. Anyone that could log into the Window OS would automatically have access to SQL.
If you have remote user accessing the MSSQL database server, you might check into using a router to setup a Virtual Private Network, VPN. The VPN would require remote user authentication via a group or username password, 168 bit encrytion, stateful IP packet inspection, and intrusion detection, and more. Cisco, Linksys, Netgear, and many other companies make router with built-in VPN. For more info on VPN, you could check the Cicso, Linksys, etc. web sites.
Leland F. Jackson, CPA
Software - Master (TM)
Nothing Runs Like the Fox
You could have SQL use windows NT/2000 security. Anyone that is not setup in the domain with a username/password would not be able to gain access to SQL. Anyone that could log into the Window OS would automatically have access to SQL.
If you have remote user accessing the MSSQL database server, you might check into using a router to setup a Virtual Private Network, VPN. The VPN would require remote user authentication via a group or username password, 168 bit encrytion, stateful IP packet inspection, and intrusion detection, and more. Cisco, Linksys, Netgear, and many other companies make router with built-in VPN. For more info on VPN, you could check the Cicso, Linksys, etc. web sites.
Leland F. Jackson, CPA
Software - Master (TM)
Nothing Runs Like the Fox
- Thread starter
- #3
NT logins are not workable for 2 reasons:
1) Not everyone on the network has an NT login.
2) We don't want all and sundry to get automatic access to the data just because they have an NT login.
I'm trying to look at data level and application level security.
1) Not everyone on the network has an NT login.
2) We don't want all and sundry to get automatic access to the data just because they have an NT login.
I'm trying to look at data level and application level security.
Hi,
If I had complex security needs, I would use SQL security. It's more work, but provides a lot more options regarding security.
If your switching to MSSQL databases/tables, using MSSQL security would eliminate a lot of coding at the VFP level. If the VFP app needed to set MSSQL scurity for users, passwords, etc, I would use sqlexec() to pass through commands to the back-end. This would be equivalent to setting at a MSSQL prompt and issueing command from the MSSQL command window.
Leland F. Jackson, CPA
Software - Master (TM)
Nothing Runs Like the Fox
If I had complex security needs, I would use SQL security. It's more work, but provides a lot more options regarding security.
If your switching to MSSQL databases/tables, using MSSQL security would eliminate a lot of coding at the VFP level. If the VFP app needed to set MSSQL scurity for users, passwords, etc, I would use sqlexec() to pass through commands to the back-end. This would be equivalent to setting at a MSSQL prompt and issueing command from the MSSQL command window.
Leland F. Jackson, CPA
Software - Master (TM)
Nothing Runs Like the Fox
- Status
