SQL Server connection

Can anyone suggest a good set of components that will allow me to connect to SQL Server without using the BDE or ODBC ? I have tried SQLQuery and find that I have reliabiltiy issues.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 Perhaps you can use "ADO"+"OLEDB" to do this.
  You Create a connection string with ADO and OLEDB for SQLServer.
I also suggest ADO&OLEDB
We are thinking about converting all our applications because the BDE smells like (Edited by Copmuter101):)
We don't wanna use 3rd party components because we think you will always encounter problems.
Good luck
MarciusPAuthor Commented:
Hmm... Can either of you provide me some information about how to implement your suggestions?
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

Has you have a D5?
If this ,you can use the ADO compenent from compenent Page "ADO" .And D5 have some demo with this.I didn't know how to finish this if you have no D5.
Diamond ADO is a good solution or use the ADO typelib directly
MarciusPAuthor Commented:
Could you provide more information about implementing this solution? Also, what are the performance implications of using ADO (which I believe sits ontop of ODBC) ?
I find Diamond ADO performs well with
SQL 7.0, it's native interface is through OLEDB so ODBC DSN's are not required. Also many update issues are fixed i.e. updating members of joined queries.

Performance is not quite as good with 6.5 though.

With careful selection of cursor locations and types I find that ADO "can" outperform ODBC. Though that may not always be the case when using default values. Other considerations are the selection of cache sizes (rowset counts) and use of multi-record databound controls (grids).

I do recommend it.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.