I'm about to create a quality control database for the entire quality control department for a mortgage company. Right now I'm doing some design work in Access 97. I will have at least 25 users if not more. I intend to use SQL Server as the back end database, with a Visual Basic 6 front end. My question is what is the best front end tool for SQL Server? Is there a difference in performance or speed when working with a VB or Access Front end? Thanks in advance for your feedback.
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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
What's the best front end to SQL Server? 2
- Thread starter Terpsfan
- Start date
-
1
- #2
My advice is that whatever front-end that you use most of the coding effort should go into the back-end. Ideally, any database access should be via a stored procedures. This will have a number of benefits:
1. your front-end code will be simpler
2. you won't duplicate complex SELECT statements in your front-end...then change one later and forget the other
3. the server can do most of the work
4. if someone else is coding some of the front-end then you can trust their db-access code. My Home -->
1. your front-end code will be simpler
2. you won't duplicate complex SELECT statements in your front-end...then change one later and forget the other
3. the server can do most of the work
4. if someone else is coding some of the front-end then you can trust their db-access code. My Home -->
-
1
- #3
"I'm about to create a quality control database for the entire quality control department for a mortgage company. Right now I'm doing some design work in Access 97. I will have at least 25 users if not more. I intend to use SQL Server as the back end database, with a Visual Basic 6 front end. My question is what is the best front end tool for SQL Server? Is there a difference in performance or speed when working with a VB or Access Front end? Thanks in advance for your feedback"
------------------------------------------------------------
If your users have access to intranet/internet -browsers, you might want to consider using ASP/VBScript. Most of your code will be server side (you can use Dynamic HTML which is client side development). You can use IIS as your server. Users will not be tied to a PC - you can use logon for security. You can easily expand number of users in or out of organization because all they need are a browser and IP connection - don't need copy of Access or .exe or .dll files on a PC. (Make sure you keep IIS security patches up to date and I would go easy on client-side code - security is one drawback to web (IMHO).
------------------------------------------------------------
If your users have access to intranet/internet -browsers, you might want to consider using ASP/VBScript. Most of your code will be server side (you can use Dynamic HTML which is client side development). You can use IIS as your server. Users will not be tied to a PC - you can use logon for security. You can easily expand number of users in or out of organization because all they need are a browser and IP connection - don't need copy of Access or .exe or .dll files on a PC. (Make sure you keep IIS security patches up to date and I would go easy on client-side code - security is one drawback to web (IMHO).
Well in my experience Delphi rules!
There is a lot to say about that, supporting jnicho02, and
my opinion, I think Delphi fills all his requirements.
And don't forget delphi has native SQL components that
are reliable, very organized (for the herencies - I'm not sure about the term it's 'herencias' in Spanish my language)
and with interesting events, methods and properties.
The answer in a word:
DELPHI
There is a lot to say about that, supporting jnicho02, and
my opinion, I think Delphi fills all his requirements.
And don't forget delphi has native SQL components that
are reliable, very organized (for the herencies - I'm not sure about the term it's 'herencias' in Spanish my language)
and with interesting events, methods and properties.
The answer in a word:
DELPHI
wushutwist
Programmer
Sorry guys but J2EE rocks house for Web Applications. I can just smell the EJBs brewing. Wushutwist
- Status
Similar threads
- Locked
- Question
- Locked
- Question
