But is it the best one?.
Main Topics
Browse All Topics
Hi.
i have to develop an application with MS SQL 2005. But, i don't know what is the best way to connect inside the Delphi 2006?.
is it necessary to use Core Lab?.
Abdurahman
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Combined with SQL Server, I personally would just use ADO since both are developed by Microsoft and thus perform quite well together. Unfortunately the ADO components provided by Delphi don't perform as well as they should so instead of using these components, I tend to just use the raw ADO API by importing the ADO type library in my project. The drawback is that you can't use the DB Aware controls this way but it has the best performance. Besides, combined with XML/XSLT and some other tricks, you can create quite interesting applications this way. That is, if you're a well-experienced Delphi/ADO Developer.
Personally, I like to use a document model for my project. Basically, this means that when the user starts the application, data is retrieved from the database server and stored in an in-memory XML file. Using MSXML and ClientDatasets I am able to work with this data and don't need any connection to the database until an update is absolutely required. When an update is required, I just synchronise the data in my XML with the database , resolving possible conflicts at that point.
The advantage of the document model is that a user could work offline with your application. The XML could be saved to a file on disk, emailed to another user and whatever more. Best of all, the user can undo any changes without these having immediate effects on the database.
The drawback is that you have to be careful with the data modifications. They don't have immediate effects so multiple users could technically be using the same data, making different modifications to it. It's not a model that is suitable for all projects. But in a project where you work e.g. with customer data, you could consider all data related to a single customer as one single document.
Anyway, the best solution strongly depends on what you're trying to build.
Business Accounts
Answer for Membership
by: hidrauPosted on 2007-01-04 at 06:10:05ID: 18243036
You can use ADO to connect.